skysight-inc/HackerNews huggingface dataset:
I think people often underestimate (or just plain don't know about) the degree to which a multiple-dispatch-based programming language like Julia effectively implies its whole own dispatch-oriented programming paradigm, with both some amazing advantages (composability [1], and an IMO excellent balance of speed and interactivity when combined with JAOT compilation), but also some entirely new pitfalls to watch out for (particularly, type-instability [2,3]). Meanwhile, some habits and code patterns that may be seen as "best practices" in Python, Matlab can be detrimental and lead to excess allocations in Julia [4], so it may almost be easier to switch to Julia (and get good performance from day 1) if you are coming from a language like C where you are used to thinking about allocations, in-place methods, and loops being fast.

Things are definitely stabilizing a bit post-1.0, but it's still a young language, so it'll take a while for documentation to fully catch up; in the meanwhile, the best option in my experience has been to lurk the various chat forums (slack/zulip/etc. [5]) and pick up best-practices from the folks on the cutting edge by osmosis.

[1] https://www.youtube.com/watch?v=kc9HwsxE1OY

[2] https://www.johnmyleswhite.com/notebook/2013/12/06/writing-t...

[3] https://docs.julialang.org/en/v1.5/manual/performance-tips/#...

[4] https://github.com/brenhinkeller/JuliaAdviceForMatlabProgram...

[5] https://julialang.org/community/#official_channels
I'm just concerned that journalists will become more like celebrities. Less concerned with the cold facts and more with giving their take.

Frankly a similar thing has already happened in the art world. Banksy, Jeff Koons, and Damien Hirst are fantastic marketers, not artists.
While you might not be calling for ostracizing the cancellers, plenty of people out there are calling for exactly that.

There's a number of terms being used ('SJW', 'woke', 'cancel culture', 'cultural Marxism', etc.) to denigrate and quell any kind of discourse that goes against conservative talking points. I'd suggest you go and watch any of the self-described 'conservative comedians' to understand the level of otherization and systematic invalidation of any views that don't match theirs. Then come back here and tell me their behavior isn't as much of a moral panic as the supposed 'cancel culture'.

The fact that it is majorly powerful self-described Christian conservatives politicians that are constantly pushing the 'cancel culture' narrative should be a hint, don't you think?
Planning permission for redevelopment has been a requirement since 1948.
How to Scale for Reliability and Trust
The publisher model gets thrown around a lot in regards to social media companies like substack. The basic line of reasoning is that, as a publisher, substack would be "responsible" for its content.

But what ways are traditional publishers "responsible" for their content? There's some internal self-imposed responsibility (e.g. someone will be fired due to insensitive tweet), but that's more politics than anything else. Large publishers regularly print patently incorrect data and narratives with no consequences. So maybe this publisher/platform distinction isn't all that meaningful
The word "now" is doing a lot of work there :) So also successful.

Do you think there was really a time that being a really successful journalist didn't require some charisma and a talent for publicity? Maybe the publication handled some of those things, but it doesn't change that they were required.
Semiconductor fabrication involves pyrophoric vapors. It's pretty dangerous.
I think once the novelty wears off and people start seeing how many subscriptions they are on, they will move to consolidated packages covering multiple writers, like Netflix for writing. Which already exists in the sense of Medium.com

Everything reverts to the mean and your point is valid - we shouldn’t expect one form of writing to have abnormally high returns to effort ratio for too long, unless there is a general shift in the value of writing by the population at large. Which given current trends towards video and higher stimulation, I would assume is less likely?

Unless one could argue there’s a huge untapped latent market of bookworms. I think there is some market to a degree as people get burned out on other forms of media, but I’m not sure if it’s large enough for substacks model to work for a significant period in the future
The vast vast majority of car owners do not want to implement their own components using instructions from a blog. I can't believe that even needs saying. Most people want an integrated car and don't care about swappable sensors or access to engine data. I know I don't.
Some friendly feedback, if they're reading this:

My profile: I'm someone interested in principle in the fediverse. I have a Mastodon account, and plan to expand my footprint when I get a chance, maybe install Peertube on my site etc. I'm not a developer for anything on it, thus am not familiar with the nuts and bolts, but I'm at least curious about it.

With that in mind, I'm not exactly sure what I'm looking at. Is this for people writing clients? And what form does this take, a software suite? If that's the case I wonder why getting started requires an email address. Some parts of the site (list of instances, list of software) seem to be very general resources, which doesn't give much more of a clue what exactly this is about. And then the FAQ answers very specific questions. There's a middle ground that feels missing to me.

I do get that this is for helping with testing, and somehow with development in general. Is this like an instance that you can point your client at, that works like Pixelfed, Mastodon etc, but gives more useful error feedback? Saying that explicitly would cover what I'm getting at.

Perhaps I'm just not the target market, but it seems like the "what is this" test needs a little more to pass for someone like me.
When I looked into doing this before I think the ultimate issue was that the C specification doesn't even give you any way to check the overflow flag.

So even if you knew your specific C implementation handled overflow properly there is no way to check the flag afterwards anyway.
Referrers can leak information about which pages the user was navigating before, which linked websites have no business of knowing.

If you want to do tracking and have control over both pages, just use a different URL, a query string, or something like that.
If the list is meant to be universal, I would strike the last two from it, and clarify that "fast enough" means, "Fast enough for the problem you're trying to solve."

Working from the bottom: Scaling well to large projects is only a concern if you expect your individual projects to become large. I've worked on monoliths, and I've worked on systems that follow more of a Unix philosophy. In the former case, we had one project with a 7 digit line count. In the latter case, it was rare for a single application's codebase to grow to more than a few thousand lines of code.

"Plenty of developers to hire from" is often optimizing for the wrong problem. In many lines of business, domain expertise is a much more valuable skill, because it can only be developed through years of first-hand experience. A new programming language, on the other hand, can typically be taught to a reasonably skilled programmer in no more than a couple weeks.

Also, when you're just starting out, the single best programming language you can pick is the one that the people actually starting the business already know the best. They will not have senior mentors to help them learn the best way to use a new language.

Finally, "fast enough" is not a single target or a strict hierarchy. I used to work at a shop where we used Python, C#, and C++. Only C++ was fast enough, performance-wise, for some problems. Only Python was fast enough, productivity-wise, for other problems. C# covered the (large) middle ground.

It's also not a strict hierarchy. At my current job, I'm in the middle of a project to replace some Java components with Python. Java has not proven to be fast enough, performance-wise, for this particular problem, while Python gets us there with room to spare.
I'm not speculating about medical diagnosis, I'm speculating on public statements from the man himself.
Oh we had this long before Rust, and most of C++ usage in new applications was displaced by safer (among other things) languages.

I think the biggest thing was that university curriculums and mainstream app development platforms (like Microsoft) stopped pushing it as hard when the level of horror got past a certain point. It used to be pretty bad. Business apps being written using MS "Active Template Library" in C++ and then used as signed ActiveX plugins on IE6-only web pages etc.
An evergreen conversation:

"I love C++." —Alice

"Oh? Which C++?" —Bob

Every successful C++ team defines its own C++ subset.
B2 is not flat rate pricing. It's $5/TB.

I understand that is a lower price than your own product, but it doesn't necessarily follow that they're losing money.

You seem to be implying that their covering the losses on storage by selling customer data. Is that correct? In which case, would you like to be a bit more specific and explicit?
> I considered using backblaze a couple of times and now I'm very happy that I eventually didn't.

Same. I ended up going with spideroak because it was too hard to figure out what other providers were even promising for privacy, and it’s been fine. I’m thinking maybe of trying rsync.net with duplicity one day
> You said that already[1], this is unsubstantiated and you declined to answer to my rebuttal.

Sorry, didn't see your response. I can answer it in two ways, subjective and objective. The subjective is "I know it when I see it," which roughly corresponds to the difficulty in determining what an unfamiliar piece of code does as well as how many language rules I need to know to figure that out. The objective one is literally language complexity, i.e. the computational complexity of determining whether a string belongs is in the language or not (i.e. whether or not it is well-formed).[1]

> you constantly have to wonder at which time the given code is gonna run

You really don't. The semantics of Zig are the same as those of Zig', which would be the language that runs comptime at runtime. The whole point of comptime is that as far as semantics -- not performance -- is concerned, you do not have to care when code would run.

[1]: There's a complex theoretical caveat here, because I believe both Zig and Rust are undecidable. So we can exclude degenerate cases from Rust, and look at the complexity of Zig' , the language I introduce in the second paragraph, which is semantically the same as Zig.
The start of the carbon cycle is one which I have found to be very unpopular to discuss, and it has a direct connection to methane in the atmosphere. Artificial fertilizers is produce through a process which takes in natural gas as its primary ingredient. The process is also a major source for methane leaks, with a large variance in claimed contribution for the global methane pollution.

For a large portion of the global Methane pollution from cattle, the carbon cycle started out with natural gas being used to produce artificial fertilizer. If we wanted to address methane pollution it would make sense to start there in order to address both leaks and the introduction of carbon into the system, but this is where politics comes in. Artificial fertilizer is not just the building block for most cattle farmers, it is also the building block for most meat alternatives and the so called "renewable and carbon free" biomass industry.

On my free time I often spend time diving in the Baltic sea, and every time I go below the surface I see the effect that artificial fertilizer has. The excess nutrient is killing the whole area, which in turn release more methane from the ocean bottom. Currently the area is around of 60,000 km2, but the effect can easily be seen in nearby "healthy" areas.
You've described NY Times and Fox News in how they write controversial things to get more traffic. They share the same world, yet have quite dissimilar front pages, because they're tailoring controversy for the value systems of their audiences. The authors on Substack don't need to seek controversy: they just need to point out the rules of the orthodoxy, and then the controversy follows them.
How to Create a Professional LinkedIn Profile That Rocks
>We are now at the point where everything matters

You are missing the point and mischaracterising the problem. Resources are finite. Human attention spans are limited. Emissions from ships in international waters are an absolutely huge problem and addressing that will make a huge impact on future climate.

Funny how no one mentions that but we are all focused on paper straws and smart doorbells.
Was Ted Koppel really a great journalist?
Antibot Is Not Accessible
Many people worry about automation would take jobs from most people, while others believe there would be always new jobs.

They're both not wrong. But the catch is, when the machine is taking over the "real jobs", the "new jobs" created are more and more let people to entertain each other. Unlike the old-time circuses that have to travel along the continent village-to-village, these entertainers can easily scale to massive audiences with the Internet, leading to information monopolies and the winner-takes-all situation.

It would only get worse over time. The current model of capitalism would not work at all for a highly-advanced society where most "real jobs" have been automated, and most people have to join the entertainment industry.

(It's actually just how average artists struggle now and in the past, but because they're minorities so people don't care enough. IMHO in a highly-advanced society most people would be more or less like artists.)
I'm not a native English speaker, but as far as I know, the word complexity in English is pretty close to its meaning in French (where it comes from). From Wikipedia:

> Complexity characterises the behaviour of a system or model whose components interact in multiple ways and follow local rules, meaning there is no reasonable higher instruction to define the various possible interactions.

This is in fact the most antithetical possible description of Rust, which, thanks to its strong type system and compile-time rules, keep the interactions between different components or features as clear and specified as possible.

Yes Rust is hard to learn, but learning curve and complexity are orthogonal concerns.
I think the idea is to replace gas appliances as they break with electric. Why? Buying electric replacements is an investment towards decarbonization: when that last gas electric plant shuts down your electric appliance is powered by solar/wind/nuclear “automatically”.

It seems like a pretty reasonable stance to take to decarbonize given the 15 yearish lifespan of most appliances and the urgency of the problem.
Of course. Investigative journalism has little to do with building an audience of paying subscribers. When the newspaper handled the business end, the journalists could focus on the journalism.

It wasn't called "loss leader" for nothing.
At the highest level, this is a leadership issue. There's a lack of someone at a sufficiently high level (eg: C-suite) that properly understands technology, and that's probably caused by the rest of the leadership team not understanding their limitations.

At a lower level, it's allowing individuals to become knowledge silos (or having a bus factor [1] of 1); lack of documentation; not having+testing disaster recovery plans; neglecting systems, code bases, and platforms; letting technical debt accrue endlessly (or worse: not even realize that's what you're doing).

How to avoid? Make sure there's a strong, competent technology leader with a vested interest in the company succeeding, and empower them to make the changes they need to.

What should that person be doing? Making sure all the stuff I just said doesn't happen.

[1] https://en.m.wikipedia.org/wiki/Bus_factor
I too am a shade-tree mechanic. It's worth noting that early electronic fuel injection didn't require any external software or device. Rather, you would use a model-specific technique to put the vehicles computer into diagnostic mode, and it would blink codes at you from the check engine light, or perhaps show the code on an LCD that was normally for another purpose. This was late 80s and early 90s stuff using OBD1, the earlier diagnostic standard.

On my Toyotas, I would need to jumper a couple pins in a connector under the hood with a paper clip, labeled T1 and E1, I recall. On my BMW, I had to turn the key to ON and then stomp the gas pedal 5 times in a few seconds. After counting the blinks, the meaning of the codes could be found in manuals. IMHO this was a great system and every bit as useful as what you get with basic OBD2 scanners, just without the scanner investment. I needed no tools to be told my catalytic converter or primary o2 sensor failed, etc.
There have been incidents in Hawaii where people successfully used a garden hose to protect their home from oncoming lava flow.
This points to a culture problem more than the language itself though.
So the tariff needs to be high enough to be absolutely ruinous. See, for example, Canada's tariff on dairy. Since Canada runs a cartel on dairy producers, Canada does set the domestic price of milk at $4/gal. This is incompatible with the US subsidy model, where it prices out to around $1.50 a gallon -- so there's a 270% tariff on dairy imports. The great thing about numbers is there's always a bigger one.
My impression at least is that the tail is a bit longer and descends less steeply on Twitch. It seems possible to have a solid middle class income through Twitch as long as you keep on the treadmill. But it also seems awfully precarious. It also seems to be becoming more intertwined with YouTube and using the latter for discovery of the former so who knows which way it’s going.
How is the experience of hiring full time engineers in different time zone?
I am running a company that helps US-based startups hire full-time employees from India. We take care of all the HR operations, benefits, payrolls and legal compliance.
What I wanted to understand is there anyone who have any experience hiring developers from India or managing distributed teams in multiple time zones.
Archaeologists find earliest colonial site in Maryland after 90-year search
Indeed, Scala looks like a language research project, more like Perl and Haskell. You definitely can use all of them in production and benefit from that, but you need both mastery and restraint in using such a language.

Golang is the opposite: it takes the ideas from 1980s with some early 1990s (Pascal, Modula-2, Oberon; CSP; garbage collection) and executes them to near perfection. It even ignores some of the obvious faults in ergonomics (if (err != null) return err; everywhere) to keep things dead simple and reasonably performant. It's much harder to write incomprehensible code in Golang, even if you try, so lack of mastery and restraint would have much less catastrophic consequences than in a highly expressive language like Scala (or e.g. C++).
And what about when apt doesn't have a package for the thing you want? You can install Spotify, Steam, Discord, Microsoft Edge, Zoom, and Minecraft with flatpak.
and P in IOT is for privacy lol.
> Then by all means don't and write your own prometheus metrics module shrug

I'm a sysadmin, not a programmer. So I don't code for business operations. I compile them to make them work. I don't have time to read all the schematics of the application to make it work, but when it comes to perl, or TCL for that matter. All files are local, if my box has air-gapped and no access to github. Then what?

> Your argument seems to be, "I don't like reading documentation."

Not at all. I have limited time to spare on documentation. It's easier for me to read the code in front in practical form then it is to read documentation written on some wiki.
How to make a sticky video on scroll like in YouTube app?
> I really wish richer nations would think more globally before they rush to such decisions.

The Danish government has no obligation to base its public health policy on what is optically best for Bulgaria. Every Danish person should be able to expect that their government will act in the best interest of Denmark.
I don't see this as a particularly bad problem in Scala tbh. Any language that is mature enough to be used for a large project will include many different ways of solving common problems. I'm old enough to remember listening to J2EE developers arguing endlessly about which GoF design patterns to use in which situations, usually resulting in using roughly all of them in one way or another so everyone could feel included.
NSMenu is gonna be the end of me (2019)
There seems to be a backlash in progress against Substack's publishing policies.

Last week I finally subscribed on Substack to an art-related list where I had been enjoying the free edition for a while. ($55 / year felt like a pretty good deal for access to more of this interesting content.)

A few days later, the writer announced that they're moving off Substack. I'll just quote their message verbatim:

"I’m planning to switch to my newsletter provider from Substack to Ghost in the near future — if I understand it right, the paid subscriptions can all be migrated, so I don’t think it’ll be a big hiccup on the subscriber end. I’ll let you know when I actually make the switch.

"It’s because I’m concerned with Substack’s marketing plan of subsidizing controversial authors (discourse here: Annaleen Newitz, Emily VanDerWerff, Jude Ellison S. Doyle, Metafilter thread), particularly a weirdly large number that can be reasonably construed as anti-trans. Plus, Graham Linehan still uses the service, despite being kicked off plenty of other platforms for documented anti-trans abuse.

"The media profiting off of platforming anti-trans views was a major impetus behind the rise of anti-trans sentiment in the UK in 2016, and the same seems to be happening in the US (broadly, not just on Substack). Yet Substack’s response seems to pretty bluntly reject the idea that they need to reconsider anything. Even if they ban Linehan in the future, I’ve lost faith in the leadership."

Personally I feel this author is doing the right thing by getting off a platform whose policies they can't support. And it makes me wonder about Substack's stickiness, because as a consumer I certainly don't care one bit which company processes my annual payment and delivers the emails.
> I was talking about what you can do with dual actuators, not product lines that already exist.

Since you didn't know they're different until a moment ago, you were talking about both. Don't gaslight.

> Each head, even at peak transfer rate, uses less than half the bandwidth of the external interface.

So two will come damn close ... today. With an expectation that internal transfer rates will increase faster than standards-bound external rates. And the fact that no interface ever meets its nominal bps for a million reasons. Requests have overhead, interface chips have their own limits, signal-quality issues cause losses and retries (or step down down lower rates), etc. Lastly, request streams are never perfectly balanced except for trivial (mostly synthetic-benchmark) cases, and the drive can't do better than the request stream allows. There are so many potential bottlenecks here that any given use case is sure to hit one ... as actually seems to be the case empirically. Your theory remains theory, but facts remain facts.