Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Koromix
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
Koromix
10y ago
Linux filesystems are not encoding aware. Paths are just treated as opaque byte strings. However, there is ongoing work add configurable safe filenames to Linux: https://lwn.net/Articles/686789/ But it won't
32.
▲
by
Koromix
10y ago
For some reason I completely missed that show, it looks great. Thanks!
33.
▲
by
Koromix
10y ago
Programming is about making a piece of hardware do what you want to do. Many people seem to forget that, or treat it as an afterthought. "Oh yeah, it's slow. Hopefully the compiler will do its magic!". Except it does not, bec
34.
▲
by
Koromix
10y ago
The reader scans all queues, without locking. If one is non-empty, then you lock it and pop an item. Only if are all queues are empty then you hit the slow path and wait on a synchronization primitive (condition variable). Of course if you
35.
▲
by
Koromix
10y ago
Neil Brown published an interesting series about Unix design mistakes a few years ago: https://lwn.net/Articles/414618/ The first part of the "Unfixable designs" article is about Unix signals.
36.
▲
by
Koromix
10y ago
mmap() tricks you into thinking you can directly access the disk. What really happens when you access the mapped data is that the CPU generates a page fault, the OS takes control, copies the data from disk to physical memory and maps the pa
37.
▲
by
Koromix
10y ago
Consumer OS I/O software stacks are completely unable to deal with this. It was fine for spinning drive latency, it's okay(ish) for high-performance SSD but the open/read/write model just cannot work that fast. It's
38.
▲
by
Koromix
10y ago
> is an ability to push asynchronous messages/events there (usually from different threads), and to get them back (usually from one single thread) – in FIFO order, of course. It is worth noting that FIFO only holds for messages comi
39.
▲
by
Koromix
10y ago
Indeed it behaves much better on a demo I found elsewhere, sorry for the inaccurate comment.
40.
▲
by
Koromix
10y ago
The overhead for a simple textarea seems significant. On Firefox there are stalls (up to 500 ms) if I type "fast". I've tested the form on http://redux-form.com/5.2.5/#/examples/simple?_k=8ukhm8
41.
▲
by
Koromix
10y ago
They are not plenty fast. You know you don't have a fast platform when the best you can do is scroll + a couple animations at the same time. And even then, HTML+JS apps often cannot do that without lag. Not saying that native apps are
42.
▲
by
Koromix
10y ago
"Does every single screen need to have 60 fps animations, with activities that launch from the exact x/y coordinate where my finger touches the screen?" This makes it sound like smoothly animating a few rectangles is hard. Th
43.
▲
by
Koromix
10y ago
People are used to the POSIX readiness model, that's all. And you can kind of make it work on Windows, even though the performance is not great. OTOH, porting an IOCP-oriented application to Linux will give you catastrophic performance
44.
▲
by
Koromix
10y ago
I only have superficial experience with it, but from what I can tell there is a huge mismatch between IOCP and the UNIX readiness/poll model, and from my experience most server programs are written primarily for the latter. You need to
45.
▲
by
Koromix
10y ago
And then you go to the Features page, with a box on the right clearly listing "GNU/Linux and Unix / Windows / Mac OS X" as supported plartforms :) With "Native look and feel" in the box just below. I disag
46.
▲
by
Koromix
10y ago
I understand this, even though the constant breaking of GTK apps after each update annoys me to no end. But you might want to discuss updating https://www.gtk.org/ and other sites for that matter. Quoting the first lines of