Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
aapoalas
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
aapoalas
1mo ago
It is not.
2.
▲
by
aapoalas
2mo ago
I believe Zig will always do bounds checks, except maybe in ReleaseFast mode?
3.
▲
by
aapoalas
2mo ago
I had an HP Mini 5102 and I absolutely loved it! I actually revived it a few years ago and used it for some modern programming tasks. I think I tried to compile rustc on it once and had to leave it on for the night, coming back to it in the
4.
▲
by
aapoalas
3mo ago
Really cool to see Zig have strong support and a stable financial status <3
5.
▲
by
aapoalas
3mo ago
Ooh, cooll to hear you got some uptake on the call for formal methods help! Or did you end up figuring it out on your own? Either way, looking forward to the followup!
6.
▲
by
aapoalas
4mo ago
Oh, I was just watching this yesterday and got a little re-energised about getting back to more active development of my DoD JS engine! Thanks!
7.
▲
by
aapoalas
4mo ago
Beyond just quite possibly being slop, this is also sloppy and confused: complaining that C++ cannot remove features because they live in the stdlib forever while listing out a bevy of features that got deprecated and then removed is just o
8.
▲
by
aapoalas
4mo ago
This bug was already reported very soon after the merge.
9.
▲
by
aapoalas
4mo ago
They have a PR (~~closed by GitHub bot as AI slop, ironically~~ this was wrong info, it was apparently closed by Jarred himself as it missed a conversion or some 20 Zig files to Rust) to remove the Zig code. I guess the answer is "no&q
10.
▲
by
aapoalas
4mo ago
Regarding the architecture documentation you have up on tsz.dev, one thing that jumped out to me was the use of the per node typed side pools. A semi-recent talk[0] had benchmarked this and found it to be a deoptimisation: he couldn't
11.
▲
by
aapoalas
5mo ago
"They're your feelings and no one else has the right to how you should feel about them."
12.
▲
by
aapoalas
5mo ago
Remember to be careful with looping lest you create an ikikieriö.
13.
▲
by
aapoalas
5mo ago
Would kernel huge pages possibly have an effect here also?
14.
▲
by
aapoalas
7mo ago
I may have not properly read the paper that said "This is not a visa, you should apply for a visa using this paper"...
15.
▲
by
aapoalas
7mo ago
I have very fond memories of Kansai airport. First time I went to Japan I ... Uhh, I didn't have a visa despite going there for exchange. The Kansai airport immigration office uttered a lot of "oohs" and "eehs", but
16.
▲
by
aapoalas
7mo ago
You and me both; never change you beautiful bastard of a language <3
17.
▲
by
aapoalas
7mo ago
If you want to take a look at some of the "big drivers", the Project Goals[1] is the right place. These are goals proposed by the community and the language developers put together, they are not explicit milestones or must-haves,
18.
▲
by
aapoalas
7mo ago
He is the Rust project lead, and the Rust project has been doing quite a bit of user, adopter, and non-adopter interviews over the past few years.
19.
▲
by
aapoalas
7mo ago
It's also been ridiculously slow for a month or two now :/ not a good time to be working on some relatively intricate performance optimisation with DevTools taking 1-4 seconds to even start the performance recording.
20.
▲
by
aapoalas
8mo ago
I was sitting behind you as you wrote this comment. I just wanted to tell you that.
21.
▲
by
aapoalas
8mo ago
F.ex. they didn't do postgresql and other DBs separately but instead just had a databases room.
22.
▲
by
aapoalas
8mo ago
Monkey's paw: you get your wish, but so does someone who wants RAII and single-use-malloc to be left behind as a leaky and bad abstractions. We all happily march into a future where only arena allocation is allowed, and when the arena
23.
▲
by
aapoalas
8mo ago
I aim to displease!
24.
▲
by
aapoalas
8mo ago
Author here: to get the compiler to help me as the programmer to produce correct code (not accidentally using handles after GC) without being massively manual, but (at least currently) accepting that it is not a guarantee and thus runtime c
25.
▲
Garbage collection is contrarian
(trynova.dev)
68 points
by
aapoalas
8mo ago
|
23 comments
26.
▲
by
aapoalas
9mo ago
Preface: I am not a compiler engineer at all, so I'm just spitballing silliness here. Avoidance of type feedback counters and such. Get LBBV to clean out the redundant type checks (Higgs proved this well, avoiding something like >90
27.
▲
by
aapoalas
9mo ago
I'm a little sad to see YJIT go down in favour of a traditional design. (Yes, YJIT isn't "deprecated" but the people working on it are now mainly working on something else. That's hardly a great place to be in.) I&#
28.
▲
by
aapoalas
9mo ago
This is Oliver Medhurst' project: https://goose.icu/ It has stable funding and a full-time development team of 1.
29.
▲
by
aapoalas
9mo ago
As a fellow (but way junior) JavaScript engine developer I'm really happy to see the stricter mode, and especially Arrays being dense while Objects don't treat indexed properties specially at all: it is my opinion that this is whe
30.
▲
by
aapoalas
9mo ago
Guidance towards correct usage: eg. If you allow `a[10] = 2` and just make the Array dense, the user might not even realise the difference and will assume it's sparse. Next they perform `a[2636173747] = 3` and clog up the entire VM mem
More ›