Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
fl0ki
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
22 ms
·
211.
▲
by
fl0ki
3y ago
This might have promise. I'd really like to see an example with a heterogeneous "select" construct, which is where a lot of these proposals fall down. Go lets users do this only over channels, so the rest of the ecosystem has
212.
▲
by
fl0ki
3y ago
> Channels are specifically designed to be a high-speed data bus between goroutines, rather than ever use more expensive and less safe shared memory. What do you mean? How do you think channels are implemented? Go is open source, you can
213.
▲
by
fl0ki
3y ago
Given this fork still boasts a 2-clause BSD license, the corporate nginx can still make the effort to backport patches. It's certainly harder than requiring a single converged development branch, but how closely they track Maxim's
214.
▲
by
fl0ki
3y ago
I find that combining context and errgroup, with due care, lets us approximate Structured Concurrency to great benefit. I just think more care is due than most people give. When a function returns, we should be able to trust that any gorout
215.
▲
by
fl0ki
3y ago
> With the shift to Arm, languages compiled for a runtime interpreter will get even more important for Microsoft. How's that? Apple and its app ecosystem just ship universal binaries, so native, heavily optimized x86_64 and aarch64
216.
▲
by
fl0ki
3y ago
Sigh. People don't even know what bikeshed means any more. https://en.wiktionary.org/wiki/bikeshedding If you think the differences between C++ and Rust are "unimportant but easy-to-grasp issues" then yo
217.
▲
by
fl0ki
3y ago
> bring in random languages Rust is hardly a random choice. You can debate its merits for some domains, but replacing C++ in most of the places that C++ is used is exactly what Rust was built for and is widely recognized as doing well at
218.
▲
by
fl0ki
3y ago
The only sets of arguments I use to git log regularly: * `git log branch` because I want to cherrypick or checkout parts of another branch. * `git log --stat` because what files changed can be a big clue for what I'm looking for. * `gi
219.
▲
by
fl0ki
3y ago
A complementary virtue is that the commit is tightly scoped to exactly one change. I still see most engineers commit whatever they had in their working directory as a sort of blanket Save Point, without any thought to how those changes can
220.
▲
by
fl0ki
3y ago
The US market in particular seems to be the worst in decades, but I'm not seeing the same in other markets. Friends in Australia hopped around in the last couple of years and are very happy with their conditions and total comp. It does
221.
▲
by
fl0ki
3y ago
Rust enums are incrementing too so that they can generate machine code with dense jump tables. If you also want the discriminant value for something, you opt into that with e.g. #[repr(u8)] and you can even override the values. Note that un
222.
▲
by
fl0ki
3y ago
You've highlighted a difference in rewrites I think is worth recognizing. urllib -> requests & urllib3 is an example of a rewrite that does not preserve the original interface, which means it can fix more things but it has to co
223.
▲
by
fl0ki
3y ago
Exactly, this is perfectly put and something I've hit several times myself. I have learned to do the exact opposite: sprint to structure the project just enough to begin to tackle the hairy stuff as soon as possible, so that any change
224.
▲
by
fl0ki
3y ago
> I'm not sure what you mean about it being too risky to add regression testing later? Sure, let me expand on that. It's uncontroversial that code has to be factored for testing, projects don't usually end up easily testab
225.
▲
by
fl0ki
3y ago
I think it was both, because I think it also worked even when it wasn't a search domain. Can anyone still at Google check?
226.
▲
by
fl0ki
3y ago
I've pulled off several large, successful rewrites so I'm going to respectfully disagree, even though I agree I have seen exactly the failed rewrites that would motivate someone to ban rewrites. The crux of my argument is that som
227.
▲
by
fl0ki
3y ago
This is exactly how a committee would design it if none of the participants had actually used an internal domain. For example, in Google, https://go/foo had "go" as technically a TLD, and the memorable suffix that
228.
▲
by
fl0ki
3y ago
> many physicists think the ultimate information limit grows like the 2/3 power of volume, instead of linearly I may have misunderstood and I'm clearly not up to speed on the literature, but even at an intuitive level, wouldn&#
229.
▲
by
fl0ki
3y ago
I know what you mean but it's not that simple. The ecosystem clearly depends on the language in a very real way. If Zig changed enough to be a deal breaker for Bun, or even stopped being maintained at all, then Bun is stranded until th
230.
▲
by
fl0ki
3y ago
Rust does keep track of where the object is alive and in scope, even if that happens to be decided dynamically, e.g. an object may only exist in a condition branch or as the result of a loop running at least once. Objects also won't be
231.
▲
by
fl0ki
3y ago
I don't recommend choosing technologies this way. Elm is one of many recent, prominent examples of how years of promising language work can still leave production users stranded, both with backwards-incompatible changes that are deal-b
232.
▲
by
fl0ki
3y ago
How? GraphQL is just another way to make query API with structured output, almost always JSON in practice. If you wanted server-side rendering, you still need another endpoint even if it happens to use GraphQL internally, just like you coul
233.
▲
by
fl0ki
3y ago
I've seen far worse crimes than that :) Example: Writing what is effectively a graph algorithm where every edge/node lookup is a string key in a hash map. Transforming the string keys into dense integer offsets once-off costs near
234.
▲
by
fl0ki
3y ago
My problem is that people use this as an excuse not to consider optimization at all initially, because they think that once they have a working version, they can "just" profile and optimize the slowest few functions to get ideal p
235.
▲
by
fl0ki
3y ago
Not sure if this is a spooky coincidence, but I happened to be reading the Rust 1.75.0 release notes today and fell into this 50-tab rabbit hole: https://github.com/rust-lang/rust/pull/113053/
236.
▲
by
fl0ki
3y ago
Also referenced in the Metro Exodus "Sam's Story" DLC because of the backstory of the two characters speaking, and nuclear weapons once again being part of the scenario.
237.
▲
by
fl0ki
3y ago
> The results of your program will vary depending on the exact make of your compiler and other random attributes of your compile environment, which can wreak havoc if you have code that absolutely wants bit-identical results. This doesn&
238.
▲
by
fl0ki
3y ago
Have you found F# jobs more abundant than Rust jobs? We might be in different bubbles. I know F# has been around much longer and is a first-class citizen in Microsoft's ecosystem, but I don't touch that ecosystem much. Shame, too,
239.
▲
by
fl0ki
3y ago
This only gets you so far. In today's software landscape, somebody is going to want to hit a HTTP JSON API to automate something in their second week, and they'll have a really rough time with how async Rust works today. Try expla
240.
▲
by
fl0ki
3y ago
I completely agree but do feel it needs qualifying. The problems beginners run into aren't usually the same as the problems experienced devs run into when adopting a language new to them, but where I see the two overlap I know somethin
More ›