Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
instig007
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
61.
▲
by
instig007
9mo ago
> handling dynamic messages the dynamic messages have to have static properties to be relevant for the receiving program, the properties are known upfront, and there's no "decades-running trap of trying to solve this".
62.
▲
by
instig007
9mo ago
When you say "any better than" are you referring to the runtive vs comptime difference?
63.
▲
by
instig007
9mo ago
You're conflating types with the encoding/decoding problem. Maybe your paying jobs didn't provide you with enough room to distinguish between these two problems. Types can be encoded optimally with a minimally-required bits r
64.
▲
by
instig007
9mo ago
The article provides a contrived example and doesn't prove that ad-hoc polymorphism reduces type-safety. Even when `Maybe [a]` is being folded via `Foldable f` the claimed type-safety isn't reduced, it's the context of the fo
65.
▲
by
instig007
9mo ago
> "Who cares?" was glib on my part, I admit. It was obviously stated from the perspective of an American relying on that power, towards other Americans. > there is no "teacher" to stop the "bullying" here
66.
▲
by
instig007
9mo ago
> being gratuitously abhorrent and should have known better. This is an incredibly stupid take, and I would vote for a legislation to penalise incredibly stupid ones before gratuitously abhorrent, and more harshly so. It would be gloriou
67.
▲
by
instig007
10mo ago
It's perfect for most Python developers actually, not just for myself, contrary to your "in practice" claim.
68.
▲
by
instig007
10mo ago
> pyrsistent is super slow, though Since when is Python about speed? > Just ran a quick benchmark Where's the code? Have you observed the bottleneck call? > Except at 10k+ items, batchup dates on 100K+ items or inserting 100 k
69.
▲
by
instig007
10mo ago
The free Idea in December 2025: no JS code completion.
70.
▲
by
instig007
10mo ago
> most software engineers are not writing banking software Many software engineers write software for people who won't like the idea that their request/case can be ignored/failed/lost, when expressed openly on the fro
71.
▲
by
instig007
10mo ago
> software engineers have egos that will not let them accept that they are not designing critical stuff > Don't write bad code, but also sometimes just getting something out the door is much better than perfect quality (bird in t
72.
▲
by
instig007
10mo ago
> and a decade of tinkering has just fatigued everyone and destroyed any momentum the language once had. it's hard to buy it, considering that many of those "fatigued" moved on Kotlin, led by their managers' bs talkin
73.
▲
by
instig007
10mo ago
> but the reason Unison is a new language is exactly to avoid the limitations of such frameworks by introducing another set of limitations that Unison docs don't state upfront, because it will affect their progression as the busines
74.
▲
by
instig007
10mo ago
> And I bet those green threads still need an IO type of some sort to encode anything non-pure, plus usually do-syntax. There's no need for the do-syntax at all. The (IO a) is no different to other generic types that can be fmap-ed,
75.
▲
by
instig007
11mo ago
If you ever need this kind of stuff, you'll be better off building your own distributed interface by using plain regular GHC Haskell and https://haskell-distributed.github.io/
76.
▲
by
instig007
11mo ago
> std::variant and std::optional are not nearly as ergonomic or safe to use as rust equivalents. > but I also use rust daily and you cannot really make a straight faced argument that c++ is catching up. I mostly use std::ranges, lambd
77.
▲
by
instig007
11mo ago
> The range of problems where C++ is unequivocally the superior solution is getting smaller. The range of issues where the superior solutions offer language features superior to the features of modern C++ is getting smaller too.
78.
▲
by
instig007
11mo ago
> Once you get to that point, you might as well create and learn a different language. Nope, it's still incredibly valuable to be able to c++14 and c++26 two different translation units and then later link them together (all without
79.
▲
by
instig007
11mo ago
Sweden isn't famous for good tech salaries and stock grants though, even among the best/high profile engineers.
80.
▲
by
instig007
1y ago
> orders.c.id you don't need .c. in recent releases, you can just use the same model attributes as in orm.
81.
▲
by
instig007
1y ago
how exactly do you compile to sql?
82.
▲
by
instig007
1y ago
It's not heavy. The abstrations allow for consistent query compositions from reusable expressions. Demonstrate how you do conditional query building for everyone to witness the way.
83.
▲
by
instig007
1y ago
> Building a framework on a non-async foundation (flask) in 2025 is bizarre. Assuming that non-blocking sockets require a special language syntax that breaks seamless compositionality of functions is a lack of fundamental knowledge. No w
84.
▲
by
instig007
1y ago
skill issue
85.
▲
by
instig007
1y ago
> but I wanted something more lightweight it's called "sqlalchemy core" https://docs.sqlalchemy.org/en/20/core/
86.
▲
by
instig007
1y ago
> if you can write compilers anything that involves composing functions is weak beer > screwing around with functions and macros doesn't hold a candle to what you learn from the Dragon Book. --- So, what is it that you learn from
87.
▲
by
instig007
1y ago
> We gave China everything - we allowed their people to study at our universities, we allowed their tourists, we gave them virtually full access to our economic market I'm impressed by their generosity (whoever you're referring
88.
▲
by
instig007
1y ago
> Many simple scripts at my work [...] For some unit tests it's 45 seconds > I spend a lot of time rewriting the python logic in C++, which makes it 100x faster Nice! Your workplace didn't care to pick a better tool for the
89.
▲
by
instig007
1y ago
> We tried laissez-faire unregulated markets in the 1920s and it didn't go well for anyone but the robber barons. yes, let's keep creating too-big-to-fails instead and reward them with bailouts for their mismanagement and borde
90.
▲
by
instig007
1y ago
> Haskell is suitable for, and designed for, bleeding edge experiments, not for practical usage The notion of practicality depends on what one wishes to practice. You, for instance, are practicing FUD spreading, it's practical for y
More ›