Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Mawr
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
55 ms
·
931.
▲
by
Mawr
4y ago
The market disagrees with you. How come there are billions of dollars spent on all these knowledge workers around the world every day when they could be replaced by this expert-level AI? I'm not sure where this idea of LLMs being intel
932.
▲
by
Mawr
4y ago
Why wouldn't they? The brake simply overrides the accelerator.
933.
▲
by
Mawr
4y ago
> it was just a right place at the right time kind of thing Scammers abuse this principle by sending out texts to the tune of "Your package is on hold until you pay.". The chances a random person is expecting a package at any
934.
▲
by
Mawr
4y ago
I'm more afraid of flying than driving despite knowing the numbers involved. Irrational fear is nothing to be proud of.
935.
▲
by
Mawr
4y ago
> People are scared of nuclear energy. "But the people are retarded." [1]. "The proximate cause of the disaster was the 2011 Tōhoku earthquake and tsunami, which occurred on the afternoon of 11 March 2011 and *remains the
936.
▲
by
Mawr
4y ago
> Pedantic analysis of DMV regulations is absolutely essential. If you think following the most basic driving safety rule is 'pedantic', please don't drive. > Clearly any dolt practicing defensive driving would anticipa
937.
▲
by
Mawr
4y ago
The difference is that not reading the TOS will not kill you. It's also not just some arbitrary rule, it's a fundamental principle based on the rules of physics.
938.
▲
by
Mawr
4y ago
The recommended following distance is "Never get closer than the overall stopping distance." [1], so even if the car in front somehow went from 70mph to 0 instantly, you should be able to stop. [1]: https://assets.highw
939.
▲
by
Mawr
4y ago
> The yoke is very comfortable to rest your hand on while FSD is enabled Seems like the opposite is true: https://youtu.be/-QBWfw_nkr0?t=152
940.
▲
by
Mawr
4y ago
> Are you saying these drinks machines only dispense water? Kind of? https://youtu.be/lr4MmmWQtZM?t=349 The healthy/unhealtly food availability ratio in the western world is like 10%/90% whereas in Japan it see
941.
▲
by
Mawr
4y ago
> But a modern airliner has so many complex automated systems that expecting a pilot to fully understand all of them is unreasonable. Yes... > In both cases, the pilots assumed that the autothrottle would increase thrust during a go-a
942.
▲
by
Mawr
4y ago
> "Converting this to micromort language, an individual living in New York City has experienced roughly 50 additional micromorts of risk per day because of Covid-19. That means you were roughly twice as likely to die as you would ha
943.
▲
by
Mawr
4y ago
Here's an annoying one: https://github.com/sublimehq/sublime_text/issues/1054
944.
▲
by
Mawr
4y ago
Phones are toys, cars are tools. Completely different design requirements.
945.
▲
by
Mawr
4y ago
"I got fired over a variable name...." - https://old.reddit.com/r/cscareerquestions/comments/dpcfns/i...
946.
▲
by
Mawr
4y ago
> But as far as I understand golang's memory internals, they still offer you to use the copy-based stack directly ("var some SomeStruct;") or to allocate things directly on the heap (via "new(SomeStruct) / make(S
947.
▲
by
Mawr
4y ago
Think of it in context. A passer-by seeing someone smash a window will 100% call the police. Glass shattering makes quite a bit of noise as well and leaves behind a clearly broken window. Meanwhile, lockpicking has a chance of looking no di
948.
▲
by
Mawr
4y ago
> Has the Go team hit on some GC algorithm that has escaped the notice of the entire compiler-creating world since 1995? It's like the saying about recycling: "1. Reduce 2. Reuse 3. Recycle". Just like in real life, it
949.
▲
by
Mawr
4y ago
It's substantially safer as well.
950.
▲
by
Mawr
4y ago
Great, except: 1. The type is merely a weak hint that you should check .Valid before you use the value, there's no enforcement: https://go.dev/play/p/nS8RxGujMBk It's much better when the struct members
951.
▲
by
Mawr
4y ago
> It felt like you were really in a place, and the lack of HUD [...] In a word - immersion. The vast majority of RPG games suck at it. In-your-face tutorial pop-ups, GPS quest trackers, complex HUDs, full-screen menus, etc. For a taste o
952.
▲
by
Mawr
5y ago
> I didn't get that desire for purity that you gleaned from it. 'Folks who develop an allergic reaction to "big balls of mutable state without sum types" tend to gravitate towards languages that gives them control ove
953.
▲
by
Mawr
5y ago
> This article was, yes, a little aggressive in tone A little? "[...] but I remember fondly the time an audience member asked the Go team "why did you choose to ignore any research about type systems since the 1970s"?"
954.
▲
by
Mawr
5y ago
It's the opposite - pointing out that X can just as well be implemented in language Y is the irrelevant point because anything can be implemented in any turing complete language. Where languages differ is what they make easy to use, or
955.
▲
by
Mawr
5y ago
> What an extremely convenient template to dismiss any nuanced argument against "worse is better". Nuance is exactly what I'm arguing for, there's none in the article. > You even get to question my credentials a co
956.
▲
by
Mawr
5y ago
> > in practice, Go seems to have fewer error handling bugs than exception-based languages > > This is based on? By explicitly annotating functions as fallible the language hints to the programmer that errors need to be accounte
957.
▲
by
Mawr
5y ago
The author fundamentally misunderstands language design. He picks an arbitrary design constraint, in this case correctness, and argues that any language that does not provide 100% correctness is bad. He uses Rust for his examples, a languag
958.
▲
by
Mawr
5y ago
> There are a jillion reasons to do things that are chores. > Do I want to clean my house? Yes. Is it still a chore? > Do you seriously perceive any chores as not worth doing? None of these are relevant as to whether 'chore&#x
959.
▲
by
Mawr
5y ago
> [...] if you try to access the Option value and fail to handle the error correctly, [...] It's consistent with the way Go's error handling works. Turns out it's not anywhere near as much of an issue as you might think. I
960.
▲
by
Mawr
5y ago
1. Missing spaces around operators like "==". The first code example has them, but the author proceeds to remove them with no mention as to why. 2. More than one statement on a line: int f(int x){ int v; if(
More ›