Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
yxhuvud
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
20 ms
·
301.
▲
by
yxhuvud
1y ago
FWIW, using the same approach as in the article, ie io_uring, is one of the few ways to actually reach anywhere close to that 1 million, so it is not as if they are competing concerns.
302.
▲
by
yxhuvud
1y ago
Well, nowadays there is https://www.phoronix.com/news/Linux-RWF_UNCACHED-2024
303.
▲
by
yxhuvud
1y ago
Eww, pretending to support utf8 matchers while not supporting them at all was not pretty to see.
304.
▲
by
yxhuvud
1y ago
Nothing stops the jvm from caching hashes even if the hashes are unique per process invocation.
305.
▲
by
yxhuvud
1y ago
The point wasn't that it should be treated as a sequence of not, but that with good base abstractions you can move the decision of what to do, and how, into the data structure itself, rather than having to have the language decide for
306.
▲
by
yxhuvud
1y ago
No, that seems like language bloat. Better to make your language have internal iterators, as then data structures can add their own logic that matches their need for iteration. Then special cases don't need additional syntax.
307.
▲
by
yxhuvud
2y ago
Main issue isn't that it break stuff but that it tend to be pretty slow to compile with it.
308.
▲
by
yxhuvud
2y ago
Also I wonder how easy it will be to shoot oneself in the foot. It may be easy to accidentally make it to a string too soon and not get the proper escapeing.
309.
▲
by
yxhuvud
2y ago
The flip way to argue that is that one way to get good legislation is that some level of transparency is in place so that people can make informed opinions on what is good.
310.
▲
Crystal 1.16.0 Is Released
(crystal-lang.org)
3 points
by
yxhuvud
2y ago
|
1 comments
311.
▲
by
yxhuvud
2y ago
Notable changes being the addition of execution contexts which will be game changers for multi-threaded programming in Crystal.
312.
▲
by
yxhuvud
2y ago
10% is still a lot. Counter tariffs will still happen.
313.
▲
by
yxhuvud
2y ago
The anthem of my country claim us to be free, silent and green. And oh, that people used to talk about us and that despite they don't anymore we are still a pretty nice place to live.
314.
▲
by
yxhuvud
2y ago
In any case, it is clearly not following from his definitions of what a subtype is, since as soon as something depends on memory size the interopability is lost.
315.
▲
by
yxhuvud
2y ago
I hope this will be packaged into shared libraries at some point so that languages that isn't rust will get access to it.
316.
▲
by
yxhuvud
2y ago
All languages have patterns. They differ some between languages as language features dictate what problems need conceptualized solutions that are different from what the language provides. There are also lots and lots of domain specific pat
317.
▲
by
yxhuvud
2y ago
So essentially pushing the work to the TLB? Well, if there are people building moving GCs that manage to retain stable pointers that way, why not use it for a circular buffer as well. > The downside is that reallocation would be really s
318.
▲
by
yxhuvud
2y ago
Whatever. Allocation is slow enough that I don't care about a noncontended lock. Make things work by default and if you want to gain performance by not allowing multithreading then that should be possible and easy. But safety first, as
319.
▲
by
yxhuvud
2y ago
What i wonder is when any main stream distro will wake up and change their default allocator away from the very dated glibc.
320.
▲
by
yxhuvud
2y ago
While I do agree with the general sentiment, I think the default should be to use the safer ones that can handle multi threaded usage. If someone wants to use a bad allocator like glibc that doesn't handle concurrency well, then they s
321.
▲
by
yxhuvud
2y ago
Funny, cause the situations where I've had to replace glibc is always that it is a long running server that allocates often. Glibc: Ballooning memory, eventually crash. jemalloc: Stable as a rock.
322.
▲
by
yxhuvud
2y ago
So why not ask the prospective customers for the right to fetch and use their data? If it gives them better rates then people have plenty of incentives to allow them to continue.
323.
▲
by
yxhuvud
2y ago
I have a guideline where I tend to put a name on a result if and only if it changes the type of the data compared to the previous step. It works well.
324.
▲
by
yxhuvud
2y ago
This is a valid concern I also reacted a little bit on. One thing to note though is that it is often possible to tell such chains to be lazy and only collect the end result at the end without ever generating any intermediary arrays. Which r
325.
▲
by
yxhuvud
2y ago
It also include gaming machines. Of course, Apple also don't make those.
326.
▲
by
yxhuvud
2y ago
I'd order a "fuck off espresso" in that situation just to see what happens.
327.
▲
by
yxhuvud
2y ago
No. Some languages use . for thousand (or even hundred) separators.
328.
▲
by
yxhuvud
2y ago
What makes it good is the tradeoff between how well it solves the problem compared to how easy it is to maintain. And people learn how to write better code as they get more experienced, but old projects are seldom rewritten using the learni
329.
▲
by
yxhuvud
2y ago
It can also mean "We have not changed this because we don't dare to do that, or it is too much work and we just have to live with the bad decisions made 25 years ago". And that is the last code you want to copy.
330.
▲
by
yxhuvud
2y ago
No, because then you end up reading old C-code that are IFDEF mazes and think that is good code. No, to see good code you usually have to look at what experienced people write when they get to greenfield something new.
More ›