Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
renox
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
181.
▲
by
renox
3y ago
It's a subject which interest me very much as I'm the father of boys who were misdiagnosed as autist (turns out that twins do have a different development but doctors don't know about it). On one hand if it's real that
182.
▲
by
renox
3y ago
> 3. A vocal minority of change-averse people complained with little to no factual basis Little to actual factual basis?? 1) How do you explain the time it has taken?? 2) prioritising "shallow security" over "accessibility
183.
▲
by
renox
3y ago
> Wayland's design requiring accessibility to be reimplemented by every DE I'm not a big Wayland fan (quite the opposite truly), but I don't know if this is true: if there's an accessibility protocol made for Wayland
184.
▲
by
renox
3y ago
I got stuck at level 5 (define your print function), I'm not a Python expert..
185.
▲
by
renox
3y ago
What's really sad is that not having overloading "ON" by default is a good idea, but it doesn't mean that language has to stop there, it's really simple to have a small language feature which would say that a #every
186.
▲
by
renox
3y ago
> Stradivari violins, hand-crafted by members of the Italian Stradivari family, are legendarily considered to have a superior and unique sound compared to violins made with even the most modern techniques. I read somewhere that Stradivar
187.
▲
by
renox
3y ago
LWN
188.
▲
by
renox
3y ago
Nobody said they're impossible but believing that they would make sense economically even after they switched to maglev was the dumb part.
189.
▲
by
renox
3y ago
Couldn't this kind of things be caught by type checking? 1-indexed vectors should be different type than arbitrary offset vector (implicitly convertible in one way only).
190.
▲
by
renox
3y ago
Replace theory with abstraction/mental model/concept and then the blog becomes quite obvious. Yes, grokking code is hard, especially low level code where the WHAT to do is intertwined with the HOW.
191.
▲
by
renox
3y ago
Ex-vim user here. No, I've tried it many times and finally I'm using VSCode for good: I don't think that vim is good enough as an IDE unless you accept to change your workflow to adapt to vim. I've also tried SpaceVim
192.
▲
by
renox
3y ago
It depends on the users and the typewriter but it could be quite frequent: I remember an old typewriter which didn't have é so you had to use e and ' to make it, same for ê, etc.
193.
▲
by
renox
3y ago
> It's important to respect their religious liberty even if you disagree Respect in what sense? My stepsister is religious so I "respect" her by not talking about this subject. But if she ever talk with me about religion I
194.
▲
by
renox
3y ago
Given that Zig is memory unsafe it isn't either a good general purpose language. IMO a good GPR is memory safe (no C, C++, Zig), is easy to use(no Rust), has strong static typing (no Perl, Python, Ruby) and is "stable" (no Sc
195.
▲
by
renox
3y ago
The problem with postfix * for dereferencing is that it would look like a multiplication.. That's why I would have used a postfix @ for dereferencing.
196.
▲
by
renox
3y ago
I find quite funny that one reason why its "fill..ellipse" example is hard to read is because it's setting global variables and this is never discussed in the webpage. > my_nice_color = color(161, 219, 114); ellispe(65, 50
197.
▲
by
renox
3y ago
This reminds me of Arcan where the goal number 1 is robustness, which is probably a good idea given the complexity of GUIs.
198.
▲
by
renox
3y ago
> Wayland never fails to impress me with how much stuff has still been left out That's the problem when you replace a desktop system with something which has been designed for the embedded use case, Wayland's proponent always b
199.
▲
by
renox
3y ago
In the general case you're right, in this case where the optimization is related to the usage of uninitialized memory I don't think that you're correct. Of course this means that the programmer must 'think like an optimi
200.
▲
by
renox
3y ago
Last release 2021 with gcc10 :-(
201.
▲
by
renox
3y ago
I'm not sure about what is really 'simplicity'.. If I program in assembly languages I don't need a huge compiler to generate the executable so the system is simpler but for the programmer it's also more complex beca
202.
▲
by
renox
3y ago
Note that in Zig an unsigned overflow is also an UB in release unchecked mode. Don't like it? Don't use unchecked mode or use wrapping operators..
203.
▲
by
renox
3y ago
What's strange is that if you had started with a Lisp, it would have been much simpler! And yet few people think about using a Lisp for their DSL.
204.
▲
by
renox
3y ago
What's a bit sad is that now with Zig/Idris you can finally easily make a type checked printf but in the meantime Python use fstrings which are much more ergonomic than prinf and AFAIK you can't make statically checked fstrin
205.
▲
by
renox
3y ago
Yes, I'm French too and when I was on holiday in Thailand, in a mall I noticed that there were people in wheelchairs shopping, my first thought: in France they wouldn't be able to be here because the accomodations are so bad.. It&
206.
▲
by
renox
3y ago
I think that the leaks are/(were?) 32bit only no?
207.
▲
by
renox
3y ago
I still didn't see in the documentation what's supposed to happen in case of overflow..
208.
▲
by
renox
3y ago
>It's a good place to start since empty threads should show you the maximum advantage of goroutines. That's the part I'm not so sure..
209.
▲
by
renox
3y ago
A good part of the article is about a non-realistic microbenchmark (nobody spawns empty threads ).. Also measuring the performance difference with threads making some work would be more interesting IMHO.
210.
▲
by
renox
3y ago
> New designs should be described in terms of the design space, so you can immediately convey their relative position compared to other point solutions. Expect a lot of statements of the form: “all solutions must do X”; “solution Y is j
More ›