Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
spinningslate
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
spinningslate
2y ago
What you do will, in part, depend on how you feel about 2 things: 1. Mozilla is now an advertising business - see e.g. links in this El Reg post [0]. 2. How you feel about the alternatives. Behind the PR bluffing of the last few days, #1 is
32.
▲
by
spinningslate
2y ago
"When you upload or input information through Firefox, you hereby grant us a nonexclusive, royalty-free, worldwide license to use that information to help you navigate, experience, and interact with online content as you indicate with
33.
▲
Mozilla is going to collect a lot more data from Firefox users
(osnews.com)
2 points
by
spinningslate
2y ago
|
3 comments
34.
▲
by
spinningslate
2y ago
The US firearm mortality rate was 5x that of the nearest high-income countries in 2019 [0]. The US had 120 firearms per 100 people in 2018 with 80% of all homicides being gun-related [1]. Those statistics may not be wholly attributable to d
35.
▲
by
spinningslate
2y ago
Yes! Fond memories. I put it firmly in the Betamax category: superior technology that lost out for political/marketing reasons.
36.
▲
by
spinningslate
2y ago
thank you for writing this. I cut my teeth on OS/2 in the early 90s, where using threads and processes to handle concurrent tasks was the recommended programming model. It was well-supported by the OS, with a comprehensive API for pro
37.
▲
by
spinningslate
2y ago
> even in business code which does not want to maintain its worker pool or spool up a new BEAM process every time it needs to send two HTTP requests at the same time. Just... no. First off, I'll bet a vanishingly small number of ap
38.
▲
by
spinningslate
2y ago
Agree. The remaining comments boil down to: 1. "It's not visual, it's text". Yeah, but: how many "visual" representations have no text? And there _are_ visuals in there: the depictions of state space. They
39.
▲
by
spinningslate
2y ago
indeed, good description. Noting that vue etc. are MVC in the browser , with (typically) calls to json http endpoints on the back end to read/write data. JQuery was born in a time of server-side rendering (SSR) where, in essence, MVC
40.
▲
by
spinningslate
2y ago
Indeed. OTOH, "focus your main code on the happy path, and put your error handling in the supervisor tree" is unfortunately a bit less pithy. Shades of "boring technology"[0] which might better be described as "cho
41.
▲
by
spinningslate
2y ago
this is a controversial topic - right up there with static vs dynamic typing. I found your post helpful and well written, but in the end I still find myself supporting Bob's blue/red delineation as a helpful articulation of the ke
42.
▲
by
spinningslate
2y ago
I think gp's point is that bif[n_] == 0 for all n_. A 'smart' optimser would recognise this and so the time to compute would be (a) constant irrespective of the value of n_, and (b) instantaneous because the function call ca
43.
▲
by
spinningslate
2y ago
This thread is a great illustration of the reality that there are no hard rules, judgement matters, and we don't always get things right. I'm pretty long-in-the-tooth and feel like I've gone through 3 stages in my career: 1.
44.
▲
by
spinningslate
2y ago
From TFA: > If anything, the need has increased as social media and changing advertising landscapes have made shallow, sensationalistic reporting all the more lucrative. And your comment: > There were people among us who would gladly
45.
▲
by
spinningslate
2y ago
what's in the "middle of lidl" this week? Drill bits, car shampoo and a kubernetes cluster. Nice.
46.
▲
by
spinningslate
2y ago
or: the EU is serious about citizen privacy and addressing the flagrant disregard for it that the major adtech players have shown. If LIDL can compete on price/features/performance _and_ comply with the laws, then good luck to th
47.
▲
by
spinningslate
2y ago
you've made the performance argument before and I don't refute that C# shows up better in benchmarks than BEAM languages. Or many others for that matter (including Python). The reductive argument there is that if performance is t
48.
▲
by
spinningslate
2y ago
>I hope your opinion about C#'s task system has improved since the last time[0], given what Gleam (and, in many ways, Elixir) does looks practically identical :) Well no, not really I'm afraid. My reservation has always been w
49.
▲
by
spinningslate
2y ago
> The difference is that in Go you are expected to explicitly send the result via a channel or some other data structure and then synchronize the completion of the execution, where-as with tasks you simply await that. That may be be the
50.
▲
by
spinningslate
2y ago
The site covers all bases. The content of the script is shown on the landing page - and you have to visit it to see the instructions to run it. The comment also explains how to do it through through the configuration UI. That means you hav
51.
▲
by
spinningslate
2y ago
yes, definitely. I find it helpful to think of usability and friction as an inverse square law relation [0]. Small increases in friction (x-axis) cause dramatic drop-off in usability (y-axis) to begin with, then correspondingly less so.
52.
▲
by
spinningslate
2y ago
With no disrespect to the book that's the subject of this thread as I haven't read it, but Bob Nystrom's Crafting Interpreter [0] is a fantastic book. It covers all phases in compilation, including both an interpreter and a
53.
▲
by
spinningslate
2y ago
The very first sentence of that article got me excited: >I’ve been noodling on a static type system for my current hobby language. As an inveterate language tinkerer for decades, Crafting Interpreters is like the intersection of Class A
54.
▲
by
spinningslate
2y ago
> HN loves to sign praises to it yet never looks into the detail nor has performance intuition to know that the use of predominantly interpreted languages is frequently inappropriate (note how Erlang is next to Ruby): And you seem singul
55.
▲
by
spinningslate
2y ago
> I maintain a frontend framework written in gleam and it's all grand For anyone interested, that framework is Lustre[0]. It looks interesting: An Elm-inspired approach to SPAs on the front end, compiling Gleam to javascript. Back
56.
▲
by
spinningslate
2y ago
this. Erlang's concurrency support is one of those things you can't unsee. Going back to sequential-by-design languages (which is pretty much every other industrial quality language bar go[1]) just feels cumbersome: C/C++&#
57.
▲
by
spinningslate
2y ago
that's fair to an extent, and shows why it's difficult. Do we want the platforms to be the sole arbiter of truth? No, definitely not. Equally, editorial control where the sole driver is profit - with no accountability for socie
58.
▲
by
spinningslate
2y ago
> given that 1) It's not in Meta's interest Somewhat glib answer is it needs to be in their interest. Section 230 means the social media platforms are insulated from liability for the content they publish and promote. It was
59.
▲
by
spinningslate
3y ago
> You'll typically have an idea of whether or not a function performs IO from the start. I think GP's point is: why does that matter? Much writing on Async/Await roughly correlates IO with "slow". GP rightly po
60.
▲
by
spinningslate
3y ago
yep, it's great. One of my favourite things about HN. I, for one, will lament these days when the AI overlords take over and we just ask AlexaSiriGPT to write all our code in the same breath as turning on the radio.
More ›