skysight-inc/HackerNews huggingface dataset:
My point is that Lower Decks did not prove the theory that Disco is in a different universe. So it is just as much evidence as before this episode that Disco is not in the main universe. In fact tehre is no proof that TNG and TOS and Lower Decks are in the exact same universe and not in very similar parallel universes. Unless if on screen was shown that all 3 have same quantumm signature.

I think it would make sense Disco is different universe , would make the fans happey too , but this episode brings no proof for it , though in a trek form or reddit I would let the fans to enoy this "fake news" , here or in Daystrom subreedit I am though expectic more logic.
Conservapedia already exists.
I had thought LSP was basically an editor-independent way to implement language editing modes. Since I mostly use languages Emacs already has modes for, I haven't pursued LSP, but I figure that it's there if I need it. Thanks.

PS, I would be interested in seeing a serious Ada vs Rust comparison by an actual fluent user of both.
Just to reiterate stuff said in the other comments because your comment is maybe deliberately misrepresenting what was said in the thread.

Their entire cluster was 2.4 million CPU cores (without more info on what the cores were). This includes not only Ruby web applications that handle requests, but also other infrastructure. Asynchronous processing, database servers, message queue processing, data workflows etc, etc, etc. You cannot run a back of the envelope calculation and say 0.85 requests per second per core and that is why they're optimising Ruby. While that might be the end result and a commentary on contemporary software architecture as a whole, it does not tell you much about the performance of the Ruby part of the equation in isolation.

They had bursts of 280 million rpm (4.6 million rps) with average of 2.8 million rps.
I 100% use LSPs and other modern tooling, but I find it weird as well too. Like, if I found out a favorite author of mine wrote everything on paper first I'd find that amusing and quirky.

Obviously a developer not using LSPs can be competitive against someone who doesn't (though that's not always the case).

Though if someone is truly bothered by others tool preferences, they should take comfort in the thought that if things really are as they believe, then these people should be driven out of a job for failing to keep up with the times. "Great," you should think, "one less person of competition on the market."
I don't understand why I should have had any such idea, given that I've been programming for thirty-five years and yesterday was literally the first day I even heard (well, saw) the word "observability" used this way, never mind that it isn't in the title. I also already suggested an alternative and I don't see what would be wrong with it.
My gripe with the post is that there is no objective "cognitive load" solution. Arguably this varies from 1 person to another.
The only small arms cartridge plant that Ukraine had originally was in Luhansk, so it got captured even before 2022. It's only this year that they've got a new plant operational, but it produces both 5.45 and 5.56.

And Western supplies are mostly 5.56 for obvious reasons, although there are some exceptions - mostly countries that have switched fairly late and still have substantial stocks of 5.45, such as Bulgaria. But those are also limited in quantity.

So in practice it's not quite so simple, and Ukraine seems to be aiming for 5.56 as their primary cartridge long-term, specifically so that it's easier for Western countries to supply them with guns and ammo.
Insane take. What about the people with life threatening infections in those countries? Just collateral damage?
So with semi-colons, you have three basic options:

1. Not required (eg Python, Go)

2. Required (eg C/C++, Java)

3. Optional (eg Javascript)

For me, (3) is by far the worst option. To me, the whole ASI debate is so ridiculous. To get away with (1), the languages make restrictions on syntax, most of which I think are acceptable. For example, Java/C/C++ allow you to put multiple statements on a single line. Do you need that? Probably not. I can't even think of an example where that's useful/helpful.

"Boilerplate" becomes a matter of debate. It's a common criticism with Java, for example (eg anonymous classes). I personally think with modern IDEs it's really a very minor issue.

But some languages make, say, the return statement optional. I actually don't like this. I like a return being explicit and clear in the code. Some will argue the return statement is boilerplate.

Also, explicit type declarations can be viewed as boilerplate.. There are levels to this. C++'s auto is one-level. So are "var" declarations. Java is more restrictive than this (eg <> for implied types to avoid repeating types in a single declaration). But is this boilerplate?

Common Lisp is where you lose me. Like the meme goes, if CL was a good idea it would've caught on at some point in the last 60 years. Redefning the language seems like a recipe for disaster, or at least adding a bunch of cognitive load because you can't trust that "standard" functions aren't doing standard things.

Someone once said they like in Java that they're never surprised by 100 lines of code of Java. Unlike CL, there's never a parser or an interpreter hidden in there. Now that's a testament to CL's power for sure. But this kind of power just isn't conducive to maintainable code.
Fair call. In any case I think you'll find things moving towards bootc and away from having to know rpm-ostree at all. The bootc documentation for fedora is pretty good and the Universal Blue project has built some awesome distros that use bootc.
In most of the world, by population, the regulatory structure of society is so weak that there is no way to achieve this. Antibiotics are available without prescription, licensed doctors of skill are rare, and patients are insistent on antibiotics for everything. In most developed countries doctors are already parsimonious with antibiotics and generally won’t prescribe them unless an infection is observable. But in most of the developing world it’s prevalent to over administer antibiotics either through clinics are directly at the unregulated pharmacies.
Interesting - I'm curious whether you feel that Xarray covers these use cases already?

https://xarray.dev/

Especially as I've said before that Hyperspy shares so many features in common with Xarray that Hyperspy should just use Xarray under the hood.

https://github.com/hyperspy/hyperspy/discussions/3405
Yep, basically “I agree with this statement a lot.” It’s very much an “online Americanism.”
I'm all in on bluefin-dx too, and Bluetooth is working fine for me in my lenovo x1 carbon. Fingers crossed you can sort your issue out.
"Domain-Specific Languages" by Martin Fowler and Rebecca Parson might be interesting: https://martinfowler.com/books/dsl.html
> Types of cognitive load - Extrinsic/Intrinsic

This neatly mirrors the central ideas presented in Out of the Tar Pit [0], which defines accidental and essential complexity.

Reading this paper was probably one of the biggest career unlocks for me. You really can win ~the entire game if you stay focused on the schema and keep in touch with the customer often enough to ensure that it makes sense to them over time.

OOTP presents a functional-relational programming approach, but you really just need the relational part to manage the complexity of the domain. Being able to say that one domain type is relevant to another domain type, but only by way of a certain set of attributes (in a 3rd domain type - join table), is an unbelievably powerful tool when used with discipline. This is how you can directly represent messy real world things like circular dependencies. Modern SQL dialects provide recursive CTEs which were intended to query these implied graphs.

Over time, my experience has evolved into "let's do as much within the RDBMS as we possibly can". LINQ & friends are certainly nice to have if you need to build a fancy ETL pipeline that interfaces with some non-SQL target, but they'll never beat a simple merge statement in brevity or performance if the source & target of the information is ultimately within the same DB scope. I find myself spending more time in the SQL tools (and Excel) than I do in the various code tools.

[0] https://curtclifton.net/papers/MoseleyMarks06a.pdf
When states fail crypto isn't much of a safe harbor. It's just a fiat with crazy interchange fees, except one with a public ledger.

Also mining will come to an end soon as it becomes impossible to meet the energy demand.
Flatpak doesn't auto update out of the box on any distro I have used.
> but I guess this means that its those areas where farming was once feasible and where people now live are becoming more arid?

Yep, it's an agricultural catch 22. Arid regions where people live are generally formed by mountains absorbing rainfall. When that water washes down, it carries nutrients and forms very agriculturally productive alluvial plains like in the Nile delta (although the reason for that desertification is Hadley cell circulation, not mountains, iirc). It's both why Egyptian civilization was so successful and why so many artifacts survived as long as they were stored away from the delta. The longer the region has been arid, the thicker the layer of usable nutrients and some areas like California are also on top of ancient oceans with thick layers of fossilized organisms providing calcium carbonate and phosphorus. These regions also tend to have favorable temperatures that support multiple growing seasons per year and without plentiful water, there are far fewer other plant species to compete with.

In wetter regions, that water instead washes most of the nutrients into the ocean to the point where areas like the Amazon are so nutrient poor that organisms evolve unique adaptation like pitcher plants and the whole ecosystem depends on intercontinental dust that's carried all the way from the Sahara (the Bodélé Depression especially) [1]. Farming is still plenty feasible in wetter areas (Brazil and the PNW have plenty of agriculture for example and it's the whole basis for rice farming) but it's nowhere near as productive

[1] https://www.nasa.gov/centers-and-facilities/goddard/nasa-sat...
> with the aim of making MDN more accessible to non-experts and helping to take new web developers from "beginner to comfortable".

I love this. Maybe there's still hope... Been doing web development for over a decade and I'm still not "comfortable" with it >.<
Christopher Nolan's next film is based on 'The Odyssey'
No, I mean for the developer of the web browser.

I have worked on a web browser. It's fricking hard. Remove JavaScript and DOM entirely, and it gets much easier.

Now if you start to implement select parts of the spec, it becomes even harder when something fails to know whether it's a feature (because you don't like that part of the spec) or a bug (because you misunderstood or misimplemented some part of the spec that you wanted to implement correctly).
I signed up for Kagi this morning and I’m already in love.
Bitcoin is still useless except as a gambling ticket or illicit money transfer. And even those use cases are on shaky ground.
I have an issue with complex conditions with or without local variable labels for readability. You really shouldn't have them at all.

At one time, they used to teach that functions should have one entry-point (this is typically a non-issue but can come up with assembly code) and one exit-point. Instead of a complex condition, I much prefer just early returns ie:

// what's going on 1
if (condition1 || condition2) {
return;
}

// what's going on 2
if (condition3 && condition4) {
return;
}

// what's going on 3
if (condition5) {
return;
}

// do the thing
return;
It's a call for others to take note of the important or profound message being highlighted. So more than just "I agree".
Agreed. That’s why I’m glad the new administration is prioritizing establishing a strategic Bitcoin reserve, for when the shit really hits the fan.

(/s if you couldn’t tell)
I've had some C# code inflicted on me recently that follows the pile of garbage design pattern. Just some offshore guys fulfilling the poorly expressed spec with as little brain work as possible. The amount of almost-duplicate boilerplate kicking around is one of the problems. Yeah it looks like the language design encourages this lowest common denominator type approach, and has lead into the supplier providing code that needs substantial refactoring in order be able to create automated tests as the entry points ignore separation of concerns and abuse private v public members to give the pretense of best practices while in reality providing worst practice modify this code at your peril instead. It's very annoying because I could have used that budget to do something actually useful, but on the other hand improves my job security for now.
I mean if you like Java that's fine, to each their own I guess. But the thing that makes a codebase nice to maintain or not is how nice the code are is, nothing to do with language. If you try hard can you make a bit Java codebase easy to maintain? Probably. If you go in to maintain a random big Java codebase will you have a good time? No.
The Humble Virtues of a Simple Private Jet
Written in the style of Henry David Thoreau
The original copyright holder can enforce what they like
I think people who know all the answers to which components they would like are tech-savvy enough to assemble it themselves, and don't need to be handed a boilerplate.

What would be useful, though, is making a site for people who don't know the answers. Guide them through the options, pros/cons, why they would make different decisions, and then give them boilerplate as well as resources for learning more, hiring help, etc.

You also would need to be more robust than just front-end/back-end/database. At the very least, add in auth and payments. Probably subscription services of some kind. All those add-ons that people would need to think about should be part of it.
I think the UN or governments themselves should get into the business of bad business medicine. The fact drug companies are prioritizing research of chronic medications is an obvious outcome of our current structure. The government or quasi governmental organization can continue to subsidize industry research and buy licenses for discoveries they then productionize at cost. This wouldn’t directly compete with industry and it would incentivize public private research across large areas of otherwise unprofitable areas of medicine such as this.
Not everyone has the skills or knowledge to disassemble their laptop. I haven’t had a removable easily replaceable battery since I feel 2006ish. My current one requires 8 security screws on the bottom, a bracket removed, and even I had some issues when I did a swap earlier this year.
Is that a question?

It's alright for people to like what they like. It's alright for me to point out that they're mentally captured by a propaganda corporation.
Interview with Niels Dossche: PHP, HTML, the DOM, and living standards
I recently went through trying to profile Rust code recently. I realized that the profiling toolchain is underdeveloped across the board - "perf", the recommended profiler, isn't cross-platform (and there aren't any profilers that I found that "just work"); visualizing traces from a multi-threaded app is not fun; there isn't an IDE plugin to highlight the problematic lines, etc.
There's a difference between trying to get it to accurately answer based on the input you provide (useful) and trying to get it to accurately answer based on whatever may have been in the training data (not so useful)
Props to you for making a cool little project, but as somebody who's been involved in Linux graphics a bit: please just let Xlib die. It's an outdated API, even if you ignore the existence of Wayland. For something like fast visualizations, you should really go with something that does offscreen rendering and then blits the result. As long as you're just drawing a bunch of rectangles, even CPU software rendering may be the better solution, though obviously modern tools should use GPU rendering.

I see your journey and how you ended up with Xlib. But I think that's really more of an indictment of the sorry state of GUI in Rust.

I know that's not your job, I just couldn't let this use of Xlib stand uncommented because it's really bad for the larger ecosystem.
I mean, consider not having images, then? Having no images is, IMO, better than having terrible filler images. Most blog posts don’t have images, and the world goes on.
right

so paying money for an ireversable increase in the background radiation level for the whole planet, and exclusion zones that will be poisinous for ever,and the literal mountains of mine waste and spent fuel, puts everything square?

right
they didn't give in, but I actually checked hospital internal guidelines for doctors, and it states 3 weeks.

They could have done some more tests or whatever, as it was maybe the worst lung issue I've had and I was really miserable. I knew that antibiotics would help, and they did. I sourced them myself.

You could say lucky guess, but after I complained to my health insurer about the bad doctor's visit, they covered the cost fully without any dispute, so they must have agreed with me with at least about maybe running some more tests...
I've sometimes seen people attack early returns and I've never understood it. To me they make things so much cleaner that it seems like common sense.
That's a really good way to get your young people to leave the country.

People will rightfully oppose attempts to penalize them into having children.
Experts warn of mental health risks after rise in magic mushroom use
It would cost so much material. I think it would be more economical to just bury it. With an automated robot of course. It would also make it a hell of a lot harder for an attacker to locate the cable. But I don't know if these already exist.
Some error handling, data logging, tied to user reporting could do a long way here. I've never looked under the hood of YT, so I have no idea of the user journey in these cases. The full picture would be only visible from the Google side anyway and it'd be up to them to figure out what combinations of capabilities are causing trouble.
I thought I'm going to read a piece about US's Child Protective Services, and clicked. Was a letdown :-)
> Code is simple, safe, ergonomic and obvious.

Dunno about 'safe' -- or at least not in the more general sense that you seem to intend, rather than the more limited sense of rust's safe/unsafe distinction. If you store an index into a Vec<T> as a usize, rather than a &T, very little is stopping you from invalidating that pseudo-pointer without knowing it. (Or from using it as an index into the wrong vector, etc...)

These problems are manageable and I'm not saying 'never do this' -- I've done it myself on occasion. It's just that there are more pitfalls than you're indicating here, and it is actually a meaningful tradeoff of bug potential for ease-of-use.
Yeah, I noticed that. I think he set up some automation for that.

I confess, I'll sometimes check out lobste.rs/recent and if there's anything interesting, pop over here to submit it.

Definitely substantial overlap in terms of posts that are interesting.
We've had massive distributions in agriculture for the last 40 years.

Are the going to offset productivity gains, and new areas being more productive?

We could almost feed 50% more humans if we had less livestock (or even just more efficient - like more pork instead of beef).

Livestock takes up almost 80% of ag land...

We're not all going to starve to death if crop yields go down slightly.
You can buy your way out of the GPL if the authors are willing to relicense.

Stallman was actually an advocate of doing this.

https://www.fsf.org/blogs/rms/selling-exceptions
Is there really a proliferation of PLs that hasn't been the case before? I recall many new languages back in 00s as well, it's just that most of them didn't live long enough for people to remember them now.
It is not an issue in the US.

It is a massive, massive issue in some very large countries.
Where was the word “scientific” mentioned in the article? I don’t think you were the target reader they had in mind when the author wrote this. I’ve been programming since 1986, and this article resonates with my experience. More abstractions, layers, and so on requires my brain to have to keep track of more shit which takes away from doing the work that brought me to work on that bit of code (bug fix, feature work, debugging, etc.)

We’re very proud of you and the hard work you did to earn your PhD, now please stop trotting it out.
I believe you're right, that was my conclusion as well. I'm not sure that that will accomplish what they hoped.

To continue my original example, I could, in theory, take this code, ensure that it works with arbitrary independent pseudo-services, create my own such services, under a proprietary licence, and distribute the whole as an aggregate, which is permitted by the GPL.

The author likely seeks to provide commercial licensing for those interested in integrating their pseudo-services as libraries, which would require either that they be GPLd or that the original code be licensed in some other way.

I hope the author achieves the success they hope for without the licensing and legal hell they may have set themselves up for. It can be a great disappointment to have one's work turned into someone else's success by a someone or someones with more legal and licence cunning than one's self.

(Note: that ain't me, I've just seen that exact scenario playout more than a fair few times....)
Just getting around to looking at this. There is a certificate in sigstore for the 8.3.41 that claims the package is a build of cb260c243ffa3e0cc84820095cd88be2f5db86ca -- https://search.sigstore.dev/?logIndex=153415340. But it isn't. The package content differ from the content of that commit. This doesn't seem like something that's working that well.
Because I don't have any other options, the DX has been like that when writing in Ruby.
A very happy Christmas memory was from when I was sick with measles as a kid (perhaps aged 5?), wrapped in many layers of blankets on my grandparents' sofa, watching the Christmas tree and listening to everyone's conversation and Christmas songs on TV. Despite being slightly feverish and covered with red dots all over, I was the most happy child.

The most _nerdy_ Christmas was when I returned to my mom's house as a student (probably Chris Rea playing when I rode home on the train.. https://www.youtube.com/watch?v=DDt3u2Ev1cI ), and the only kit within reach there was an old Atari ST 520+ with a copy of Berkeley Yacc (Bison) on 3.5" floppy disk next to it. I happened to have an (unrelated) machine learning paper in my backpack, so I dedided to reimplement the paper in Yacc on this ancient machine, which was most gratifying (no man pages, no Web, no StackExchange, ...).
For those who need it, it is a way to manage impulse control. Not everyone needs it, but some people do.

GLP-1s may regulate it (via anti addiction mechanisms observed), more data to come in that regard.
Interesting. I am in agreement

But not one word about comments, and only one about naming.

Useful comments go a long way to lessening cognitive load

Good names are mnemonics, not documentation

I have worked on code bases with zero comments on the purposes of functions, and names like "next()"

And I've worked with programmers who name things like "next_stage_after_numeric_input"
I was pretty active for a few years.

Posted one too many self-promotional posts (though still within the terms and on-topic for the community). About 5-10% of my posts that were self-promotional.

Got read the riot act by the moderator. Wrote him a note saying that part of why I participated in lobste.rs was to share others great stuff, but part was to share my own stuff too. And if that wasn't in keeping with the community he was building, I was out.

Have logged in exactly once since then (to invite someone).