Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
whizzter
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
39 ms
·
661.
▲
by
whizzter
2y ago
It fits perfectly if you look at it from a "balls" standpoint, this pilot ejected for whatever by-the-book reason when his electronics were bad and yet the airplane continued for 11 minutes just on autopilot. How would you expect
662.
▲
by
whizzter
2y ago
Not surprising since iirc you wash away parts of the normal starch and then add sugar as a binder.
663.
▲
by
whizzter
2y ago
This is probably Google's Altavista moment, by making their results crappier by the year in search of Ad dollars everyone has felt that there is a potential for search to be better and once that becomes available they'll be in a c
664.
▲
by
whizzter
2y ago
And that'd totally break down as soon as some underlying class does something you didn't expect. C++ RAII patterns and Rust's ownership systems are required for a very good reason (that the GC sidesteps but also makes all cod
665.
▲
by
whizzter
2y ago
I'm hardly missing discriminated unions (sure exhaustive checking would be nice) anymore since the introduction of switch expressions that in combination with records handles most practical cases.
666.
▲
by
whizzter
2y ago
Yeah, the Vue-like I made (other comment) was my second attempt at it and this time using just Proxy to simplify things. The first time I had tried to do it as Vue did previously with defineProperty but it was a damn mess to try to support
667.
▲
by
whizzter
2y ago
I also wondered about the complexities of implementing Vue so I made a small clone sometime ago, put it on github so one can see the moving parts of a Vue-like that supports things like arrays, else blocks,etc. The functionality needed was
668.
▲
by
whizzter
2y ago
There's apparently some dealings in process due to the tariffs being imposed on moving final assembly or trying to use their local petrol manufacturing as a leverage for avoiding the tariffs. No idea about what'll come out of it t
669.
▲
by
whizzter
2y ago
Geely made an incredibly smart move buying Volvo. Ford had run down their reputation by forcing penny pinching cheap designs, but there was still a lot of engineering prowess in-house that had gone underutilized and made them a tech-team to
670.
▲
by
whizzter
2y ago
What's the benefit over existing variants like Swagger/OpenAPI/JsonSchema ?
671.
▲
by
whizzter
2y ago
Phones has become everyday items (and as a sibling comment pointed out, gone past the DSA regulation threshhold), homeless people in the Stockholm subway will go around with crappy Androids asking for "Swish" (immediate money tran
672.
▲
by
whizzter
2y ago
Right, and that's my point about practical languages that promotes a functional style being a better choice. The requirement for purity in Haskell (due to lazy evaluation) makes anything but purity a problem, it seems sometimes that ju
673.
▲
by
whizzter
2y ago
Most of the "horrible" examples in that paper are uncommon/unrealistic constructs to prove a point, yes there are real footguns in that are analogous to them but even with junior developers around I've yet to see many in
674.
▲
by
whizzter
2y ago
While Erlang itself is pure, in practice it seems like a lot of practical mutation and state issues are tucked in other processes. Nothing wrong with it and it sidesteps the purity issues that the Haskell example in the article presents.
675.
▲
by
whizzter
2y ago
The author brings up the basically the canonical example of where OOP style design shines, and where functional programming will falter. The simple truth however is that overly going into either functional or OOP camp will hurt because stri
676.
▲
by
whizzter
2y ago
What's lacking? Specific types or schema changes?
677.
▲
by
whizzter
2y ago
For reference, to achieve what IQueryable does with 100% normal code in JavaScript you need something like Qustar that was posted here a month ago. Regular transform code in JS (Like IEnumerable) const ids = users.filter(user => user.age
678.
▲
by
whizzter
2y ago
Yes and no, the LINQ syntax being coherent between IEnumerable<> and IQueryable<> hides a lot of good magic. IEnumerable<> is regular in-memory lambdas/streams, same what you find in many places. IQueryable<> re
679.
▲
by
whizzter
2y ago
I think one really BIG factor is that built-in logical replication wasn't introduced until PostgreSQL 10 in 2017, before that you only had physical replication for master-slave but iirc that didn't work between versions so doing a
680.
▲
by
whizzter
2y ago
I'm personally a bit more impressed by the Tomb Raider port mentioned in another thread, the linked game is doom/duke3d-esque and the GBA cpu should be roughly on par with a 486sx both in terms of clock speed and instructions per
681.
▲
by
whizzter
2y ago
Interesting, seems OP bank and Nordea allows logins/registrations from their own and other banks ID apps (all separate though). Vero and Kela allows logins from mobiilivarmenne and all the bank identifiers via the tunnistautuminen.suom
682.
▲
by
whizzter
2y ago
You could always protect the signing certificates in the apps with derived passwords, still the length of passkeys practically acceptable to type in on a phone is too short to safely protect a certificate vs a bruteforce attack without some
683.
▲
by
whizzter
2y ago
My point was rather that a functional style with plain old data was always preferable, the "stink" was that early TS versions _favored_ non-functional OO style that suited the TS type system at a time when most modern JS code alre
684.
▲
by
whizzter
2y ago
https://xkcd.com/927/
685.
▲
by
whizzter
2y ago
v1 of TS had a heavy "OO"/class-based bias to it, v3 and v4 made it viable for real-world JS code but peoples perception stayed both due to those who looked early on seeing something they didn't like or the code produced
686.
▲
by
whizzter
2y ago
How long ago was this? TypeScript v1 and v2 definitely had a class-based stink to it since the typing system only handled those scenarios somewhat well. Right around when I started using it (mid 2019) there was a bunch of V3 releases that e
687.
▲
by
whizzter
2y ago
Not sure this is a good idea or not, for one it'd be awesome for doing performance oriented and threaded code in JS/runtimes, the idea seems related to how C# struct's already work (and tuples under the hood). Interop with WA
688.
▲
by
whizzter
2y ago
That would probably leave the prizes awarded in a very narrow field, also the prize is supposed to be given to the thing that has "conferred the greatest benefit to humankind". So in this case they picked something that might be v
689.
▲
by
whizzter
2y ago
He was probably considered since he is mentioned in the reasoning paper, still it could be one of those unfortunate omissions in the nobel history since those deciding the prize might have a hard time to measure impact.
690.
▲
by
whizzter
2y ago
I would retort with, stop trying to chuck a SQL database everywhere. The issue imho is that multiplayer synchronization (like Jazz) should rely on primitives(CRDT or similar) that you really can't hide under abstractions but should be
More ›