His solution and syntax remind me of Ada's variant records. Despite Ada's focus on safety, it also resorts to runtime exceptions for incompatible fields in that case. That's probably a local maximum in the language design space.
Ada offers formal verification to remove checks, they can also be removed without formal verification but that is not a sane thing to do.
Ada feels like it is more about writing the correct intent of programmers and caring more about intent than any other thing. For example, the pre and postconditions are not always meant to be 100% verifiable, its fine for them to not be verifiable, the checks are more important than the verifiablility of them.
Consumes it. If you look at the picture in the article, you'll see the steam rising above the cooling towers. Why they didn't just design the facility to use treated sewage for that purpose is beyond me. Oh yeah, capitalism and fake "don't be evil" platitudes.
It's so cool to have this split. QUIC is so capable, such a neat set of ideas for a transport. That HTTP can express itself in terms of another spec is one of the most compelling, longest-hardest won & best victories for "abstraction" that computing has seen. That we'll be able to iterate on HTTP in new ways, by having a common semantic base, keeps the future open & iterable. Huge wins.
Obligatory link to Mark Nottingham's "A New Definition of HTTP3"[1], which talks about the split of HTTP into a semantic definition in RFC9110[2] & the creation of HTTP2/RFC9113 and HTTP3 (over QUIC, this document).
> It's so cool to have this split. QUIC is so capable, such a neat set of ideas for a transport.
That's what I thought too. A while ago, I wanted to use it in an Android app. I thought this was going to be a no-brainer. After all, Google more or less invented QUIC as SPDY about a decade ago. To my understanding, since they just YOLO'd it they agreed to form a proper working group and create quic. So here we are, ten years later, Google is heavily using quic for all their web stuff, and I naively assumed that Android would've had a native quic implementation for a while now, either directly in the SDK/runtime, or some first party library from Google. Nada. There is cronet, the networking engine of chrome as a library, which does speak quic but only exposes classes and functions to speak http, so you cannot even use its quic implementation directly. I went on and had to use some C library and JNI to do it, which is just ridiculous.
Sorry for this tangentially related vent, I'm still in disbelief.
Note that even the previous draft specification (https://datatracker.ietf.org/doc/draft-ietf-quic-http/34/) was a mapping of HTTP semantics on top of QUIC. It didn't carry too many transport specific concerns - which e.g. HTTP/2 did, since it cared about flow control and other things.
I have yet to read RFC 9114, but I guess it's refinded to fit better on top of the new HTTP semantics spec (RFC 9110).
I'd be aghast to see a significant rewrite of a specification as it moves from draft to rfc. The draft, at it's end, should closely mirror the final spec.
I run it in one of my computers, the small X230. I kind of regret I went with the current; running snap takes some time and I generally do it on Sunday mornings to keep packages and system up to date.
Stable would be much better here. The system just works, is always on when I open the lid and connects to the wifi fast. A perfect system for Sunday morning HN reading marathons.
I've run OpenBSD on my Thinkpad for two years, only plugging it in at night, and everything works (sleep, resume, good battery life). Which Thinkpad model do you have? When did you last try OpenBSD? Maybe I could help.
I had/have an X220. I try it every few years and it's always the same issues. Pre- and post- cpu scaling "fix".
I have no interest in openbsd any more. Debian is significantly better in every way except for "code correctness" and philosophical license issues which are frankly irrelevant to the end user.
I gave up and bought a mac which is a certified unix and apple pays people to actually work on the non-glamorous bits. My laptop lasts nearly all day and everything works. The UX for a laptop user is orders of magnitude better in every single way.
OpenBSD is a great idea but it's a terrible laptop OS.
That's pretty impressive. I would have thought that it's only possible to support a few people on that lifestyle. Could you give some more details about how you do it?
We prefer a simple lifestyle so we omit many expenses: no TV, rarely eat out, drive older cars, have no debt payments, eat only a little meat, buy high quality clothes which last through all 5 kids, high deductibles on all insurance, save as much money as possible.
I'd be glad to answer any specific questions in private. Shoot me an email at michael@ndrix.org if you want.
I'm married with 5 kids. We live in rural Wyoming (no income tax, bought a comfortable house for $86k). We've always lived well below our income so we have no debt and sufficient savings.
I mostly choose to work on "products". That helps me focus on problems that people actually care about without any of the startup pressures. Although, I've also written several open source libraries that I thought the community might like.
I started by telling my employer that I would only work 4 days each week. I spent Fridays working on a cool idea my brother and I had. That idea proved useful enough to pay the bills so I quit my job.
I'm much more relaxed now and spend better quality time with my kids. In hindsight, it would be worth almost any sacrifice to get to this point again.
Hi - thanks for sharing and congratulations - sounds like you've made things work.
> I spent Fridays working on a cool idea my brother and I had. That idea proved useful enough to pay the bills so I quit my job.
Regarding this, it sounds like you already had a good idea of what your expenses were, and I think people underestimate how important this is.
I recently quit my job and have jumped into the unknown. Firstly knowing where all my money was going, and secondly spending about 12 months trimming off all the fat was an important part of the process to give me the confidence to try this. These days I live in one of the most expensive cities in the world with my wife for about $2000/month (and over half of that is rent). We want for little. Several years ago this figure was closer to $4000/month.
The developers are a bit accounting-nerdy, and it has lots of graphs/etc which I think would appeal to the HN crowd.
It's also very flexible. One example I can think of, my friend installed it on his wife's smartphone so she could record spending on groceries wherever she was. But my wife doesn't like this level of monitoring so I just give her a wad of cash each month and enter that as a general "cash for groceries" entry.
I've also seen people in the US say good things about Mint.com, which was not available to me here in Japan.
Normally this would be a good place to put my own 10%-off referral link. Instead I'm going to give a link to a forum thread where you can get 10% off AND someone else will then use your link:
Similarly, I went part-time a few years ago (4 days) and I would say it's been one of the better decisions I've made.
Given the typically high salaries in the dev world, working part-time is an easy path to maintaining a work/life balance which provides time to pursue personal projects.
Quick question since you have a few kids. Is real Wyoming a good place for them in terms of school and future? (really asking, no idea as I live on the other side of the pond).
I work from home so I can move anywhere, and a more rural/calm place, earning less and having more time does appeal to me, but all the good schools here are in the city and I'm not brave enough to risk my kids future on my dreams of today.
I think that our local schools are about as good as government education can get. My kids' classes range from 11 to 14 students so they get lots of 1-on-1 time with a teacher. The teachers provide extra challenges for exceptional students. The teachers and school administration are very responsive to feedback from parents. Students graduating from high school with good grades get a full scholarship to the University of Wyoming, if they want it.
Having said that, my wife and I place much more emphasis on independent learning and life experiences than on formal schooling. Because my wife and I have plenty of time, we are able to encourage their education in ways we couldn't if we lived in an expensive city. Our lower living expenses also allow us to take trips and have experiences that we feel are more valuable than book learning.
Wyoming is the least populous state in the US, it's not small either. I've driven through Wyoming and Casper it's largest city. One could call it desolate meaning very little human habitation. Or one could call it a paradise on the plains depending on your perspective. Either way, there ain't shit there. Edit: Other than Yellowstone that is.
Starting by cutting down to 4 days a week (32 hours) is a good idea. I became an independent consultant in 1998, but for the 20 years before that I worked 4 days a week (and this was for a variety of large corporations - you have to ask, firmly sometimes).
I have never regretted the lost income from reducing my work hours.
