slver

83 ms·

871.
by slver 6y ago
That's precisely what was described, wasn't it?
872.
by slver 6y ago
I thought about how I'd do this in JS, and it's paradoxically more compact and less confusing without dedicated syntax: if (leaders.some(i => i == "Yang")) { alert("Yang is a leader!"); } else {
873.
by slver 6y ago
I see the logic of this feature, and in a couple of seconds I'll be unable to understand it again.
874.
by slver 6y ago
I have to admit "happy" was not a word I expected to see in this thread.
875.
by slver 6y ago
They use a lot of Java and Scala. But I'm sure it's inevitable some teams are dogfooding Swift on the server as well. Swift is a very nice language.
876.
by slver 6y ago
What does Swift have to do with Tensorflow. It's like comparing apples and oranges.
877.
by slver 6y ago
And what libraries are those...?
878.
by slver 6y ago
It's not exactly unexpected the last mile cable for a small village to have no redundancy. The redundancy is: use your cellular connection until they fix the cable.
879.
by slver 6y ago
Nah, he wasn't, he felt pretty bad about the whole ordeal.
880.
by slver 6y ago
Tailcall optimization is compiled as a JMP, so is goto, so I'm curious where would the difference come from?
881.
by slver 6y ago
Any language can become the language for everything, if it sees enough evolution and features enter the platform. The problem with Java is that it clearly shies away from more direct memory control, and as a result it's significantly d
882.
by slver 6y ago
UML was propped up (and still is) by universities, but it was never big in practice.
883.
by slver 6y ago
You'd get equivalent performance with "goto", but not depend on implicit compiler optimizations to save you from stack overflow. I like the idea of tail calls, but I don't like it being an implicit "maybe" opti
884.
by slver 6y ago
I wish tuples didn't exist in interfaces, unfortunately every function and method argument list is one. /s I appreciate your point that people try and avoid tuples where not appropriate, but the question is why even have that oppo
885.
by slver 6y ago
You fail to account for change, and time. As functional languages often do. /s Tuples have coupling order. That's a fact. So if you have tuple [a, b, c, d], then you can maybe extend this by adding ...e, f] at the end, if your par
886.
by slver 6y ago
The industry is balkanized on it. Functional languages which tend to model closed systems, with strict types, and hence easier ad-hoc refactoring swear by tuples. OOP platforms which deal with the "outside world" a lot and so need
887.
by slver 6y ago
If developers used tuples wisely we wouldn't be having this conversation. That's the primary reason why Java has no tuples.
888.
by slver 6y ago
The trouble is that tuples are not restricted to local context. JS has made a few steps in allowing us to have objects as compact as a tuple, i.e. {foo, bar, baz}. I think we need more effort in that direction. But keep fields addressable b
889.
by slver 6y ago
I'm not sure a new language in 21st century should focus on ordered tuples as a core data type. They're fundamentally hard to debug and not evolvable. Ultimately all objects/structs/records are at their core tuples. But
890.
by slver 6y ago
JavaScript has plenty of libraries covering the basics. Here a few: https://github.com/nicolaspanel/numjs https://www.npmjs.com/package/fast-math https://smartbear.com/de/blog
891.
by slver 6y ago
Unlike everyone improvising on "what it means to be REST", no one is shoving RPC down your throat.
892.
by slver 6y ago
REST is trivial only when it's RPC by another name.
893.
by slver 6y ago
Curiously the websocket spec says the server may send 30x code during handshake, but the client is "not required to follow it". So in this case you're relying on a specific client's decision more than you're relying
894.
by slver 6y ago
The current REST practices make SOAP look like a marvel of engineering. You can tell many of the current "gurus" have no idea what came before (so they reinvented it poorly).
895.
by slver 6y ago
> I've gotten value from HTTP responses in the 300s, 400s, and 500s being handled appropriately by various tools without having to write special RPC logic for those cases. What am I missing? What exactly is behind this statement? Wh
896.
by slver 6y ago
There's a long list of API problems not addressed by HTTP/2, because HTTP/2 set out to make sites faster, it didn't set out to make APIs more "RESTful". Most advice I've heard from REST aficionados tends t
897.
by slver 6y ago
"Recursion" is part of the "how" of the "why" of "divide and conquer" :P
898.
by slver 6y ago
What happens is you learn, and next time you have a concept. That doesn't mean you stopped using recipes.
899.
by slver 6y ago
Fielding has no problem recognizing the web needs one architectural style, and small-grained data APIs need another. The web doesn't need to "die". Our infinite ignorance on what REST is and what it should be used for has to
900.
by slver 6y ago
Dataloader is an implementation quirk of a particular library, not a protocol quirk of GraphQL as a query format.

More ›