Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kerkeslager
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
31.
▲
by
kerkeslager
8mo ago
> Don't even get me started on how easy it is to get a driver's license with no clue how to drive. If they wanted to reduce deaths they should start by raising the bar on license difficulty. Retesting is vital, too. Every 10 ye
32.
▲
by
kerkeslager
8mo ago
> As you said, that doesn’t do anything since the road is designed to go 35-45 MPH, that is how fast people will go, with the exception of inflexible rule followers that drive 25 MPH and cause dangerous speed differentials. If speediots
33.
▲
by
kerkeslager
8mo ago
> OPs comment isn’t a charade, he’s pointing out that it’s a very blurry line. Sorry, it just isn't, at least not in a lot of the examples he gave. It's not ambiguous whether "sponsored by" scenes on YouTube are ads:
34.
▲
by
kerkeslager
8mo ago
It's always funny to me when people feel the need to tell us they won't be inflicting their poorly-thought-out fallacies on us any more. Don't threaten me with a good time!
35.
▲
by
kerkeslager
8mo ago
The argument you're making is known as a "perfect solution fallacy". I don't even know for sure whether I think cereal boxes displaying their contents is advertising--I'm not going to make a snap opinion on that--bu
36.
▲
by
kerkeslager
8mo ago
> AI agents mean that dollars can be directly translated into open-source code contributions, and dollars are much less scarce than capable OSS programmer hours. I think this is true, but misses the point: quantity of code contributions
37.
▲
by
kerkeslager
8mo ago
I've got a few open source projects out there, and I've almost never received any PRs for them until AI, simply because they were things I did for myself and never really promoted to anyone else. But now I'm getting obviously
38.
▲
by
kerkeslager
8mo ago
I support government funding for things that keep the population exercising. It literally saves taxpayers money by driving down healthcare costs.
39.
▲
by
kerkeslager
8mo ago
Really? Name one. Note, neither one of us is a corporation, so "we" doesn't refer to corporations.
40.
▲
by
kerkeslager
8mo ago
It's called paying for goods and services. You know, basic capitalism. I think one thing to understand about advertising is that it fundamentally breaks the way capitalists say capitalism works. If you really want capitalism to be abou
41.
▲
by
kerkeslager
8mo ago
Let's drop the charade where you pretend you don't know what advertising is. You're smarter than that, and your playing dumb act would be more persuasive if you didn't ask leading questions that clearly show you know the
42.
▲
by
kerkeslager
10mo ago
EDIT 3: Looking at Lua's overall implementation, it seems to be focused on being fast and lightweight. I don't know why Lua implemented TCO, but if I had to guess, it's not because it enables you to replace loops with recursi
43.
▲
by
kerkeslager
10mo ago
Ah, I'm not so aware of the numerical/scientific computing space beyond numpy--I will say the numpy transition was pretty quick, though. I did take the approach of writing my own OAuth using `requests`, which worked well, but I do
44.
▲
by
kerkeslager
10mo ago
What? No, I'm definitely not saying that. I'm saying it isn't very useful argue about whether a feature is a feature of the language or a feature of the implementation, because the language is pretty useless independent of it
45.
▲
by
kerkeslager
10mo ago
Well, I'll point out one thing: Your definition of "core libraries" is likely a lot broader than mine. I'm old, and I remember back in the day when Perl developers started learning the hard way that CPAN isn't the P
46.
▲
by
kerkeslager
10mo ago
> More importantly, Lua has a crucial feature that Javascript lacks: tail call optimization. There are programs that I can easily write in Lua, in spite of its syntactic verbosity, that I cannot write in Javascript because of this limita
47.
▲
by
kerkeslager
10mo ago
I don't think you're wrong per se. This is a "correct" way of thinking of the situation, but it's not the only correct way and it's arguably not the most useful. A more useful way to understand the situation is
48.
▲
by
kerkeslager
10mo ago
I'm on iOS.
49.
▲
by
kerkeslager
10mo ago
This feels to me like the scenes from the movie Don't Look Up where anyone actually pointing out what's happening gets told to calm down and be less aggressive. If people saying what's wrong plainly and clearly is "vit
50.
▲
by
kerkeslager
10mo ago
I think, for those of us who have been in this industry for 20 years, AI isn't going to magically make me lose everything I learned. However, for those in the first few years of their career, I'm definitely seeing the problem wher
51.
▲
by
kerkeslager
10mo ago
Okay... are you saying there are no problems with Firefox? And if not, are how do you propose that users get these problems fixed without talking about them?
52.
▲
by
kerkeslager
10mo ago
I'm concerned, and I am glad people keep writing about this. But the final bit in this post is really where I'm at: I have no idea where to go from here. Currently on mobile I use Orion--it's the only mobile browser I've
53.
▲
by
kerkeslager
10mo ago
I suspect it's not so much that it was considered more cost-effective, and more that it wasn't considered at all. My impression was that nobody was even allocated to work on the transition until 8 months, because that's when
54.
▲
by
kerkeslager
10mo ago
> The obvious example is the change to print from a statement to a function. It makes the language a little cleaner, but it also breaks existing code for little practical benefit. To be clear: I literally do not remember a single example
55.
▲
by
kerkeslager
10mo ago
> Get rid of the pseudo SemVer where you can deprecate functions and then break in minor releases. I agree, but I think there's a bigger, cultural root cause here. This is the result of toxicity in the community. The Python 2 to 3 t
56.
▲
by
kerkeslager
10mo ago
No--the goal was to break the API so users noticed, with an easy fix. A lot of users weren't even checking the HTTP status codes, so it was necessary to not return the data to make sure the API calls broke. We did roll this out in our
57.
▲
by
kerkeslager
10mo ago
I agree, get the API right as much as possible so it doesn't need to be deprecated. But, perfection isn't realistic. If you don't have a plan for when you get things wrong, you're failing to plan for the inevitable.
58.
▲
by
kerkeslager
10mo ago
A technique I used on a project was to change the URL, and have the old URL return a 426 with an explanation, a new link, and a clear date when the moved API. This reliably breaks the API for clients so that they can't ignore it, while
59.
▲
by
kerkeslager
10mo ago
Jesus, what a terrible idea. This is such a terrible idea that I would not hire this guy based on this post alone. What I want from code is for it to a) work, and b) if that's not possible, to fail predictably and loudly. Returning the
60.
▲
by
kerkeslager
11mo ago
This problem is actually even worse than the article identifies, because broad definitions of what a "risk" is, result in broad exclusions. The most pernicious of these problems is that women --yes, more than half the earth'
More ›