skysight-inc/HackerNews huggingface dataset:
I practice a lazy form of this: I live on the edge of a small forest, what remains of what used to be here as this town was built and grew up around it, only about 100 feet deep at widest.

I came back with a lot of wood of fallen trees, branches, and filled about a foot, to save costs on soil (a mix of coconut coir and Canadian peat; similar to a potting mix in a lot of ways). I only need to water when its supremely dry, which happens up here during the peak (and hottest) of the summer.

I live in Maine, summer is also fire season, and people coming up here (because we're the "vacation state") love to start their little dumbass campfires because they want to play their stupid little "roughing it" fantasies; when its like that, I water.

Now, the peppers and tomatoes I grow? They eat all the water I can give them, and their pots aren't rigged with hugelkulture-like techniques. Maybe I should have.
That's not what I'm saying. I'm saying that "do not kill" is falsifiable. "Do not covet the neighbor's wife" is not.
Yeah, might be too late to do anything.
I've never driven one but I follow a youtube channel that documents beta FSD, posting raw video feeds and analyzing/critiquing them, and I've noticed they've been gushing about it more and more this past year. Far more than in the past he's always talking about how its mastered very complex stuff it would have disengaged or awkwardly completed only half a year earlier. I think the platform has improved quite a bit in recent years.

Of course opinions on the internet will have been established from headlines in prior years so who knows how much impact it will have on discourse if it turns out to be the case.
Some people really like to know how things work and are willing to put a lot of time in to understanding the thing that interests them. I don't feel despair. I'm glad they have a passion and feel so strongly about something that they wish to dedicate their time to their passion. If anything, I'm a little jealous. To each their own.
The classic DOOM game over htop, the text-based process viewer
I have no sympathy for doctors. They are a part of an exploitative system, and they know and accept it. Most of them are in it for money, in the first place.

The experience that the author describes is not much different than a fancy lawyer's or that of a Wall Street finance person. They all knew about the long hours, but money is more attractive...
Having access to first party reporting from Palestinians has effectively defeated Israel’s propaganda machine for younger generations in the west.
What is the basis for your assertion on how the court is going to rule?
forever for the most part. unless you donate blood. frequently.
must be seeing how crazy aggressive north american drivers are

but the lead in gasoline is far more of a factor.
It seems it was due to the company, which acquired Pyrex, but it did recover from bankruptcy [0].

[0]: https://en.wikipedia.org/wiki/Pyrex
> If you requested this 5 years ago every would think you were crazy...

That's a straw man. Nobody was ever pushing for people to import all of libsystemd just to use the communication protocol with systemd, that protocol was designed to be very easy and simple to implement on your own precisely so you didn't have to depend on anything else, libsystemd just happened to provide an implementation too, and somebody was lazy and imported that instead, but I seriously doubt that's what anyone thought was best practice.

Contrary to popular belief, systemd isn't about linking gigantic binaries and libraries together into a giant blob like everyone things (e.g. the standard nonsense line from detractors that e.g. `systemd-resolved` is "part of systemd" as in "part of the same binary", which it isn't), but about just letting programs talk to each other, so that you can get reliable, featureful integration on your desktop instead of everything being a half-working mess of shims and ad hoc communication, and providing a centralized service that can consistently and from first principles solve certain tasks, so that you don't have to have every single daemon reimplementing their own, or a central implementation that's a big pile of preprocessed shell scripts, spinlocks, edge cases, and bullshit.

> Same as the suckless people. They were right after all.

Right about what? Right in myopically judging software quality by "lines of code" and setting nonsensical arbitrary line limits, and as a consequence confusing a (poor) map for the territory, because while, yes, "few lines of code" can make software good in some ways (less buggy, etc), it can also make it quite bad in others (less featureful, doesn't handle edge cases, brittle, annoying to use), or just be completely unrelated? Or finding every possible way to vrware software that most definitely "sucks more" for the vast majority of users that don't randomly happen to perfectly align with it, software that sucks so bad people have to maintain patch lists to make it useable, with all the inherent problems with maintainability and stability over time patches incur?

Suckless is a cargo cult of tradition following a fundamentalist interpretation of its holy texts, refusing to innovate and actually make computing better, stubbornly sticking to a model left unchanged since the 70s, which wasn't even that great back then, and proud of it.
Agreed. I tried reducing across cities first.

The problem was that the work of gathering all the temperatures for each city (before I could launch the reduction CUDA kernels) required a full parsing through the input data.

My final solution would be slower than the C++ baseline since the baseline already does the full parsing anyways.
Void Linux is, to a first approximation, "Arch without the BS". Because it ships a musl version, and because Lennart thinks anything but Linux/glibc is a niche corner case which can simply be ignored, Void does not use systemd but rather runit. (Indeed, it's the only distro I know of to officially switch away from systemd to something else.) Also, there are few, if any, distro-breaking flag days. I once blindly typed 'xbps-install -Syu' into a Raspberry Pi 2 that had fallen 2-3 years behind, and everything just chugged along and updated without a hitch.

Source: I use Void, btw.
https://simple.wikipedia.org/wiki/Identical_twins
iPhone and Vision Pro are also not future vision. Both enter a market at the high end, with established competitors. BlackBerry and Nokia had smart phones that were functionally equivalent, but they were marketed towards business users and worked best with corporate integration. Apple delivered a phone that focused on personal use. Vision Pro is entering market where the competitors are focused solely on gaming or augmented work (hololens) with a product that doesn't do either, yet... but everyone is starry-eyed about what it might enable, some day.

1980s Apple, otoh, fully in the nose.
Chechnyan state needs to go bye bye already. It's sickening what they did/are doing to gay people (and plenty of other groups).
DCE is too general.

Tree-shaking is specifically the form of DCE where you remove unreferenced functions/modules.

Especially important is that you can do tree-shaking without analyzing control flow, while by default "DCE" implies you're analyzing control flow.

And I don't think tree-shaking is a misnomer. Depending on how you visualize the metaphor, unreferenced functions are either barely attached or not attached. Shaking them off is simple and sufficiently realistic.
All the information I can find indicates that it remains available for new hookups. Of course, since April 2023, new hookups are under NEM 3.0, which is significantly less beneficial to the generator than earlier NEM programs.
If it ever gets a modern file system I could probably use it for a daily driver. But powercuts are just a fact of life here.
no malice intended, but I will take my cloud provider's managed database service.. for which we get support, SOC2 compliance, years of proven stability, no major approval needed by my organization, and budget already approved - rather than jump on the latest 'kubernetes is eating the world' fad.
Shouldn't the title be rephrased to not be clickbait?

I refuse even read it bc clickbait makes me sad but something like "Gemini 1.5 can read all the HP books at once" would be a more appropriate title for this forum, imo.
In modern manufacturing, identifying and understanding bottlenecks in the process is key to knowing how to improve throughput.

One of the best resources to learn about manufacturing optimization aka the Theory of Constraints is a novel called “The Goal” by Elyahu Goldratt [1]

[1] https://en.m.wikipedia.org/wiki/The_Goal_(novel)
Ok, so I got downvoted on this one. Fair enough.

I would concede that it's probably not that reasonable for a consumer (mostly) to handle this sort of thing. I reckon there there is some combination of:

- surprise factor for the tenant.

- a general intent to discourage offshore property ownership. Agreed, this would work a lot better in a rental market with a reasonable vacancy rate (not sub-one-percent), as then many tenants would simply say 'not my bag, g'bye'.

- tackling non-arms-length transactions (eg., renting from family to facilitate money transfer).

Now then...

I will still observe that (at least legally) there's an established obligation for purchasers to pay tax on things they buy. Everyday example: 'Sales Tax' is mostly implemented as 'sales and use tax', where technically the purchaser is liable for the tax; sales tax paid offsets the use tax owing. Generally the vendor collects and remits (ie., does not 'charge') the tax amount, and the purchaser is then relieved of the tax liability. Vendors are required to collect and remit the sales tax, so for intrajurisdiction transactions the purchasers are off the hook. (Vendors are easier to audit!).

Mail-order is an issue, but historically it's far enough in the noise that nobody bothers to check this.

This is pretty much across the board: the US implements it this way, so it's not a canuckistan thing.

Counterexample is for interprovincial/interstate vehicle purchases: the amount is big enough to be worth going after, and the paperwork ensures that it gets someone's attention. This example comes up in the press from time to time, but not in an 'omig-d, really???' framing, more in a 'be an informed consumer' one.
'Unconventional' Warfare
My despair is that you think he should have spent his effort on something you find, I assume, to be more productive than this. He’s an expert is a video game, it’s wonderful that we have the material abundance to allow that.
Getting a tattoo is a significant decision that lasts a lifetime. While tattoos can be beautiful expressions of art and identity, they can also lead to regret if not approached thoughtfully. In this guide, we'll explore 10 crucial tattoo don'ts to help you steer clear of getting inked with something you'll later regret. By following these tips, you'll ensure that your tattoo experience is positive, meaningful, and free of any "stupid tattoos."

1. Don't Rush the Decision
I tried to do this but got bitten by the fact that Python didn't support varardic type arguments... somehow never thought to just pass the arguments as a tuple!

I'll try and put together a Numpy/JAX wrapper for this, because I've been looking for something that does compile-time shape checking properly for a long time!

Still wish Python's type system was as powerful as Typescript's... it's got potential that it just doesn't live up to.
[dupe]

Lots more discussion: https://news.ycombinator.com/item?id=39988718
nice one-liner. now tell me why Iran doesn't like the US.
See this post for a comparison of Python datetime libraries. The datetype, heiclockter and whenever libraries have different types for them.

https://dev.arie.bovenberg.net/blog/python-datetime-pitfalls...
Well I'm not saying they are irrelevant in the sense that they don't provide a good model for what an ISP should be, but more so that they are irrelevant because they don't provide services to the vast majority of people.

Also a part from sogetel, those are either very small or regional. Even sogetel is regional and doesn't really provide services outside small villages and cities. That's not bad, but it's not enough to say that Canada's market isn't deeply uncompetitive. Even the US has tons of cooperative and WISPs that follow a similar coop pattern.
My guess would be not adhering to the "keep right except to pass" signs on the highway. I don't tail gate, but I do find it rather annoying when people block traffic by driving right beside another vehicle rather than passing them and clearing the lane.

So that we can all not adhere to the "maximum" speed signs on the highway to the degree that we prefer :)

I was a passenger while a friend was driving once and he said "I'm already going fast enough. Nobody should be going faster than me anyway." So there's one mentality.
Software engineering will change. Up to this point, programmers have to build software code line by code line. In the near future, in less than ten years, we will get tools that automate a big chunk of that process. Software engineers will still need to design the program but the building process will be much more automated. You'll be able to request big chunks of code that will be glued and arranged by software engineers, OOP on steroids. Basically, the programming process will be sped up greatly. Software engineers will need to adapt. It reminds me of the transition from hand-coded HTML to a designing tool that lets you draw a web page and the editor takes care of the HTML code. The HTML code produced by the editor is mostly messy but it works and it greatly automates and speeds up the frontend design process. I will even say that at some point we will have apps that will output custom apps designed and created by amateurs. It will be similar to the custom websites that are produced by companies that host sites, companies like Godaddy or Squarespace.

This means that software engineers will need to be more like software designers. They will need to focus on what people need and want rather than being handed a design and having to code it by hand. There will still be a need for software engineers but the way things are done will change. Translating what users need to apps will be much more important.

I suggest you keep up with AI's coding abilities. And you transition to a role where you can speak directly to those people who have ideas they want to translate to computer code. Those apps will include AI. We are starting to see that in the OpenAI store. However, software engineers will be able to put together much more complicated apps.

If you have the skills you might want to create apps that create custom apps for amateurs. Basically, the way I see it, a person opens an app, types in a request, and out will come out a complete app that can be used. On the backend, you can have a set number of apps that will be produced by a bot that will guide users by asking questions to a complete and working app.

We won't get to the point of the user asking for a custom-complicated app and having AI output the complete program 100% of the time anytime soon but we are inching towards it.

The big question is: What apps are needed and how abstract can they be so they fill the needs of the maximum requestors?

I suspect game software will be greatly impacted since you can create many different versions of a game but there is only a set amount of software engineering needed.

So, for the foreseeable future, we will still need engineers but the role requirements will change.
Great car.

Similar feelings.
Actually their stated reason for making the site is that they don’t like the politics of openbsd devs

> Because the OpenBSD community is notorious for not being nice and welcoming:
I am pretty sure leaded gasoline for use in cars was banned a while ago, at least in the United States. Now to be fair there are definitely people who still deal with the lingering effects, is that what you’re referring to?
You're suggesting that the only "correct" stance if one has studied history outside of TikTok is to support Israel?
Apparently I'm a white man with too much money cause I like buying and playing pogeymanz.
>If your goal includes long-term maintainability then should refactor for simplicity and consistency. Removing unneeded code and unneeded tests is a good thing.

I agree with this in principle, but I think people disagree about what is needed. One person might look at a good set of tests and think it's a waste of time, but if it actually hits the right points then it's probably worth keeping. I think if unit tests are feasible and can hit a bunch of cases that would be hard to recreate otherwise, then unit tests are far superior.

>"Design the structure of your [unit] tests to be contra-variant with the structure of your production code. ... The structure of your tests should not be a mirror of the structure of your code."

That's a nice ideal. But as with the refactoring issue, it may be impossible to test a thing without recreating some of that structure. That's why we have mocks.
Why care, when there’s so many out there?
RAG (Retrieval Augmented Generation) systems are powerful, but building and deploying them can be tricky.
Cognita aims to be a user-friendly and modular solution that addresses common RAG challenges.

In Search of a True Production-Grade Complete RAG framework

Issues with current frameworks:
Chunking & embedding jobs often need separate setup, but not built-in in current frameworks known to Author as of now.
Deploying query services for production can be complex
Handling model deployment (language models, embedding models) lacks built-in support.
Vector databases can be tricky to deploy for scalability.
No single, ready-to-use template for easy adoption

Disclaimer: These issues may have been addressed by other frameworks, not known to Author as of this writing.

How Cognita Solves These Issues
Cognita balances customization with ease of use.
Scalable design to integrate breakthroughs as they happen.

Cognita — A Library for building modular, open source RAG applications for production
Modular Design: Break down RAG into steps for easier management and updates.
Reusable components: Parsers, loaders, etc., to save time across projects.
Streamlined Deployment: Cognita handles the nitty-gritty of production systems.
Scalability: Components scale independently to handle increased traffic.
User-friendly Interface: Even non-technical users can play with RAG setups.
API-Driven: Cognita works well with other systems.

Cognita Components

Indexing Job
1. Data Loaders
What: Fetch data from various places (folders, databases, etc.).
Why: RAG needs data to work with!
2. Parsers
What: Turn different file types into a common format.
Why: Makes it easier for the RAG system to process everything.
3. Embedders
What: Create code-like representations of text for fast comparison
Why: Helps find the most relevant info for your question.

Metadata Store
What: The 'brain' of the system, storing configuration details
Why: Keeps your RAG organized and easy to manage.

LLM Gateway
What: A 'translator' for different language models.
Why: Lets you switch between models without re-coding everything.

Vector DB
What: Stores embeddings for super-fast data searches.
Why: Efficient searches are key for large datasets.

API Server
What: The coordinator that handles user questions and generates answers.
Why: It connects all the pieces of the RAG system together.

Excited for Part 2: Coding with Cognita!
Not to disagree with any of your points, I'm skeptical of the proportion of NPs that can safely practice any medicine at all. I've met one competent PA, one PA who didn't understand basic human anatomy, and an PMHNP with a PhD who had seemingly no knowledge of pharmacology at all. Then I stumbled across some forums about 'noctors' with horror stories about real doctors taking patients suffering from malpractice by NPs.
Well, to play the example out...

Stopped car in unexpected place.

1 car in front of your vehicle, between you and the stopped car.

Assuming the car in front of you switches lanes around the stopped car with 1 car length of space between it and the stopped car.

So 2 car lengths + your personal gap for you to slow down.

So you could be going no faster than 20mph worst case (0 personal gap).

The issue is that the car in front of you doesn't need to stop, so can potentially "suck you in" at an unsafe speed, before you realize you'll need to come to a complete stop (assuming your lane change is blocked).
Hi.

Thanks for notifying me.

I fixed it.

Can you access my resume now?
> It’s automatic cruise control + lane keep assist backed by radar, camera, GPS, and laser scans of highways.

If that doesn't count as AI, then we have No True Scottsman'd the term to be meaningless.
theres so many of these me-too links now ive just largely begun to ignore it

its soft spam
those straws are made from a pretty neat material:

https://en.wikipedia.org/wiki/Polyhydroxyalkanoates
One doesn't have to be old to know and appreciate classic games.
> Or simply voting in a new politician when everyone hates the current one.

Oh, we already know how this one works. People generally like their elected representative, because that's how they won in that district. The district has e.g. a large employer, and the representative makes sure those jobs for the people in the district aren't lost. Even though that's the very thing people in other districts are complaining about, and in order to get that one thing the representative had to betray the citizenry in 250 other subtle ways to get votes from 250 other districts.

This is why federal legislation was originally meant to be limited in scope and require approval from both the House and the Senate, the latter of which was meant to be appointed by the state legislatures and thereby more inclined to reject that kind of populist vote buying and expansion of federal power. But we changed all that without thinking it through and now we suffer the consequences.
Interestingly, both IE and NN had `box-sizing: border-box;` as default behaviour, and at least for me that was sensible behavior. Probably a better decision at that point would have been to update spec and add a quirks mode other way around.
I live outside Seattle. We frequently get outages because trees fall on the lines. As most of where I live is glacier carved terrain, the soil conditions are very difficult for both undergrounding cables and for tree root establishment. When there is sustained heavy rains, the ground saturates, and if there are high winds afterwards, trees fall over.

I'm worse off than many, because I live on an island, and my electric service comes in across the water from a penisula. There's an awful lot of non-redundant paths through the penisula. On the island, there is no redundancy either, but there is a plan to create a ring between the three substations, which should help.

Most of my outages are only a few seconds. At the substation, they have reclosers [1], circuit breakers that will open when shorts or abnormal currents are detected, and then quickly reclose (thus the name) as many shorts are transient.

But when a tree falls on the line, that needs a truck rolled out to investigate, and often another one or two to repair. And conditions are similar across the area, so if one tree is on a line, there will be many. My local infrastructure is low priority because it serves few customers.

Ice storms are pretty nasty too, because then you've got potentially a lot more trees falling, and also hazardous road conditions that prevent or slow repair work.

When I lived in other places, power outages were much more rare. I would have never considered a whole house generator in those places, but I have one here and most of the houses I looked at had them. I would certainly install one if there wasn't one already.

[1] https://en.m.wikipedia.org/wiki/Recloser
not sure if Tesla is really the future of EV they are in serious trouble