4,711 karma · joined May 2, 2014
The project I'm most excited about in recent years is htmx. Sadly I've yet to have the opportunity to work on any real projects with it. Some day, fingers crossed!
Impossible to maintain, but damn if he couldn't churn out some quality works. Bug laden, sure, but the core ideas were great – at times even brilliant. There was a certain beauty to the chaos.
Prettier wasn't around then, and code for matters weren't much of a thing at all really. Can't help but think if that would've helped or stymied his process. Certainly would've helped the rest of us though!
This person is not just a good engineer but a solid politician.
Ahead of its time, clearly!
It wasn't perfect, for example the fact that it was just a single bar meant it was hard (but not impossible) to use accurately without looking, but to me it really was a step in the right direction.
I hope they bring it back at some point, maybe in a way that appeases the Fn crowd as well so we can all be happy. Maybe a few physical buttons with an embedded screen a la stream decks, and a smaller bar in the center for more fluid things? I don't know. All I know is I miss it dearly.
Point being: they've put a lot of effort into modelling the different tractors and first time I used the in-vehicle perspective I was amazed at all the screens and knobs and dials and levers and what not. They don't really do anything in the game, it's just for show, but man they are complex beasts clearly.
Then again, I can definitely see the value of at least some of these features. Like you spend an inordinate amount of time just making sure you get maximum yield from a field, while keeping costs low, so having a screen tell you how much fuel you're consuming per turn or whatever is actually pretty useful.
Anyway, I absolutely agree – farmers are incredible! I have a whole new appreciation for farming equipment and farmers in general, just from playing this silly game.
- peer pressure
- group think
- financial motives
- fear of the unknown (Sam being a known quantity)
- etc.
So many signatures may well mean there's consensus, but it's not a given. It may well be that we see a mass exodus of talent from OpenAI _anyway_, due to recent events, just on a different time scale.
If I had to pick one reason though, it's consensus. This whole saga could've been the script to an episode of Silicon Valley[1], and having been on the inside of companies like that I too would sign a document asking for a return to known quantities and – hopefully – stability.
The impact of any waves higher than maybe a meter is likely to make the software take you in for a rather rude landing, and quick stop.
It's unlike any boat of that size I've piloted, it was very heavy and it never felt like you were totally in control, with some small but quite noticeable latency between input and action. Felt more like piloting a larger ship than a small speed boat.
The fact that it felt like you were at the mercy of the controlling software meant it became a very anxious ride as soon as you ran into a bit of choppy waters.
When flying it was a very nice ride, but when you're not you have to go very slow or you quickly run out of battery. It was not particularly pleasant doing 3-4 knots in choppy waters, even if it did seem rather stable presumably due to the wide base, low height and deep rudders (foils).
Fine boat in calm seas for sure, but I wouldn't use it for anything else. Should do fine in fair weather in central Stockholm though.
I'm kidding, mostly. The engineer in me is bothered by it, but the part of my brain that cares more about design and branding understands that 0x1de would cause inconsistencies in the branding elsewhere. (E.g. 0xDocs: https://docs.oxide.computer)
For example, let's say I have an api at `/weather` which when requested with the header `accept: application/json` returns something like:
{ "temperature": 25, "unit": "c" }
Now if I open that same path in a browser, I get an html page displaying the day's temperature in a nicely formatted way for humans to read.Or another case, I want to version an API, such that I can provide different representations based on the version requested. So I look for `accept-version` and if it's `v1` for example I get the `v1` version. GitHub does this, as a real world example: https://docs.github.com/en/rest/overview/api-versions?apiVer...
As an example: `application/json` and `text/html` respresentations of a single resource may render some of the same bits of data, but the actual rendering process is entirely different. Even if the content type is the same, you may render completely different output based on other parameters, like a header used to select between different profiles of said content type, or even just something simple as `accept-language`.
If it's not possible right now, is there any plans to support routing based not just on method and URL, but on headers as well?