E.M. Delafield's "The Diary of a Provincial Lady", a collection of her 'Provincial Lady' series
E.M. Delafield's "The Diary of a Provincial Lady", a collection of her 'Provincial Lady' series
if foo ... else bah, but probably doesn't fit the styoe of the Go grammer.What I absolutely hate is this proposal. Making
? to magical™ things, making the code harder to read and reason about is bonkers.
if foo ... else bah, but probably doesn't fit the styoe of the Go grammer.What I absolutely hate is this proposal. Making
? to magical™ things, making the code harder to read and reason about is bonkers.
Und die TYPO3-Core-Entwickler nehmen gefühlt jeden fancy Shice mit, den sie gerade finden. Das reißt dann immer wieder Prozesse ein oder es muss ein gigantischer Aufwand betrieben werden, damit "grundlegende" Funktionen wieder hergestellt werden.
In den Kommentaren ist dann immer nur zu lesen "Tja, Pech. Gibt's nicht mehr. Sei froh, dass wir 'ne undokumentierte Schnittstelle dazu im Code versteckt haben. Bau's dir selbst."
Und der OpenSource-Gedanke ist bei einigen Erweiterungen (die als Quasi-Standard gelten) auch nur noch zu erahnen. Da müssen teilweise Abos abgeschlossen werden, damit einige Funktionen genutzt werden können.
Es wird auf jeden Fall nie langweilig.
That's my alt-feed by the way! 😉
That's my alt-feed by the way! 😉
s
const value = some?.deeply?.nested?.object?.value
but for handling errors returned by methods. So if you wanted to chain a bunch of function calls together and if any error return immediately. It would be something like this:
b:= SomeAPIWithErrorsInAllCalls()
b.DoThing1() ?
b.DoThing2() ?
// Though its not in the threads I assume one could do like this to chain.
b.Chain1()?.Chain2()?.End()?
I am however infavor of having a sort of ternary
? in go.PS. @prologic for some reason this is eating my response without throwing an error :( I assume it has something to do with the CSRF. Can i not have multiple tabs open with yarn?
#running #treadmill
#running #treadmill
#running #treadmill
foo := "eggs"
if bar {
foo = "spam"
}
Or:
var foo string
if bar {
foo = "spam"
} else {
foo = "eggs"
}
To my eye, this just would look a lot nicer:
foo := bar ? "spam" : "eggs"
Or at least as the Pythons do it:
foo = "spam" if bar else "eggs"
The ternary operator especially shines with relatively short expressions.
Mit dieser absoluten Katastrophensoftware vor dem Herrn haben wir mal ein Studienprojekt gemacht. Die hat alle Vorurteile komplett übererfüllt. Angefangen von Fehlerseiten, die statt 4xx oder dergleichen immer mit HTTP 200 ausgeliefert wurden oder auch, dass das generierte HTML leider einfach ungültig war. Über die Implementierung von Löschen durch einen Deleted-Schalter in der Datenbank, das Speichern von Passwörtern im Klartext bis hin zu völlig umständlichen Bedienungskonzepten. Alles hat immer brutal viele Schritte gebraucht. Das Zeilennummernrumgeeier im TYPO-Script erinnerte eher an Basic. Uns kam es auch so vor, als ob man damit nicht ernsthaft was sinnvolles machen könnte.
Zu allem Überfluss hatte irgendwer noch ein ganz hundsmiserables Buch ausgegraben, das als Vorbereitung dienen sollte. Ich kann mich zum Glück weder an den Titel noch den Autor erinnern, aber ich weiß noch, wie das komplett inkonsistent geschrieben war. Anfangs gabs mehrere Seiten zu Unicode und UTF-8 wurde angepriesen, aber alle Beispiele haben dann auf ISO-8859-1 gesetzt. Gezeigter Beispielcode war häufig unterste Schublade. Selten hab ich so merkwürdige Erklärungen gelesen: „Wenn Sie die Sicherheitswarnhinweise stören, kommentieren Sie doch bitte im Quelltext die
die()-Funktion in $ZEILE aus.“ Oder ein anderer Klassiker: „Ausgeschrieben würde der Code wohl folgendes tun…“. War sich der Autor also nicht ganz sicher, ob sein Codeschnipsel vllt. doch in Wahrheit was ganz anderes tut.Seit diesem gigantischen Trauma (das hat mich wirklich sehr nachhaltig geprägt, wie man Dinge nicht machen sollte) hab ich erfolgreich einen Bogen um das TYPO3-Universum gemacht.
Ich kann nur hoffen, dass es zwischenzeitlich ein wenig besser geworden ist. Aber Deinem Kurzbericht zufolge scheint da ja immer noch der Wurm drin zu sein. Mein Beileid! :-(
O Chega ficaria com 17%, a IL com 4%, o Bloco de Esquerda e a CDU 3%, e o Livre e PAN com 2%."
O Chega ficaria com 17%, a IL com 4%, o Bloco de Esquerda e a CDU 3%, e o Livre e PAN com 2%."
o autor é Kostya Petrenko 
o autor é Kostya Petrenko 
o autor é Kostya Petrenko 
Fingers crossed that this doesn't happen a third time today.
- My public server receives mail.
- Either my desktop PC or my laptop fetches new mail (via mpop) into a maildir.
- That maildir gets synced to other machines via unison (I used Git for that purpose for 13 years, unison is a bit faster).
Sending mail works similarly:
- One of my machines sends mail (via msmtp) and stores it in the maildir.
- unison syncs that to other machines.
What I like about that is that I don’t have to keep the mail files on my server. If my server crashes (never happened so far), I can upload a new blank OpenBSD image and use config management to set it up. I actually don’t make backups of my mailserver/webserver. 😅
Regarding IMAP, well, I don’t actively dislike it (other than our server at work being very, very slow, but that’s probably not IMAP’s fault). It’s more that I don’t have a need for it. 🤔
- My public server receives mail.
- Either my desktop PC or my laptop fetches new mail (via mpop) into a maildir.
- That maildir gets synced to other machines via unison (I used Git for that purpose for 13 years, unison is a bit faster).
Sending mail works similarly:
- One of my machines sends mail (via msmtp) and stores it in the maildir.
- unison syncs that to other machines.
What I like about that is that I don’t have to keep the mail files on my server. If my server crashes (never happened so far), I can upload a new blank OpenBSD image and use config management to set it up. I actually don’t make backups of my mailserver/webserver. 😅
Regarding IMAP, well, I don’t actively dislike it (other than our server at work being very, very slow, but that’s probably not IMAP’s fault). It’s more that I don’t have a need for it. 🤔
- My public server receives mail.
- Either my desktop PC or my laptop fetches new mail (via mpop) into a maildir.
- That maildir gets synced to other machines via unison (I used Git for that purpose for 13 years, unison is a bit faster).
Sending mail works similarly:
- One of my machines sends mail (via msmtp) and stores it in the maildir.
- unison syncs that to other machines.
What I like about that is that I don’t have to keep the mail files on my server. If my server crashes (never happened so far), I can upload a new blank OpenBSD image and use config management to set it up. I actually don’t make backups of my mailserver/webserver. 😅
Regarding IMAP, well, I don’t actively dislike it (other than our server at work being very, very slow, but that’s probably not IMAP’s fault). It’s more that I don’t have a need for it. 🤔
- My public server receives mail.
- Either my desktop PC or my laptop fetches new mail (via mpop) into a maildir.
- That maildir gets synced to other machines via unison (I used Git for that purpose for 13 years, unison is a bit faster).
Sending mail works similarly:
- One of my machines sends mail (via msmtp) and stores it in the maildir.
- unison syncs that to other machines.
What I like about that is that I don’t have to keep the mail files on my server. If my server crashes (never happened so far), I can upload a new blank OpenBSD image and use config management to set it up. I actually don’t make backups of my mailserver/webserver. 😅
Regarding IMAP, well, I don’t actively dislike it (other than our server at work being very, very slow, but that’s probably not IMAP’s fault). It’s more that I don’t have a need for it. 🤔
No, honestly, I don't think that there is anything wrong with the current approach. I don't see any wins of any of the proposals I've come across.
if err != nil {
...
}
basically accounts for <1-3% of your codebase in the first place.
The entire thing (_fuss_) is really just pathetic IMO.
if err != nil {
...
}
basically accounts for <1-3% of your codebase in the first place.
The entire thing (_fuss_) is really just pathetic IMO.
? garbage. I don't want to be rude, but honestly wtf is wrong with people and making languages harder to read?! 🤦♂️
? garbage. I don't want to be rude, but honestly wtf is wrong with people and making languages harder to read?! 🤦♂️
var f os.File
if f, e = os.Open("foo.txt"); e != nil {
log.Fatal("error opening file; %s", e)
}
im not sure if its much better.
Here it is: https://docs.mills.io/ix4qDHMnQUSPxZ5tXz12Vg?view
It's very rough and needs much more work, but essentially I want to propose the following change to the language's grammar:
f := os.Open("foo.txt") or (e error) {
log.Fatal("error opening file; %s", e)
}
Here it is: https://docs.mills.io/ix4qDHMnQUSPxZ5tXz12Vg?view
It's very rough and needs much more work, but essentially I want to propose the following change to the language's grammar:
f := os.Open("foo.txt") or (e error) {
log.Fatal("error opening file; %s", e)
}
Camioneta de uma empresa chamada Balerma
Camioneta de uma empresa chamada Balerma
Camioneta de uma empresa chamada Balerma
#running
#running
#running