skysight-inc/HackerNews huggingface dataset:
It does seem a very strange position when today's sensibilities are applied.

I do understand the point of view when I think back. Today, Unix-like systems are everywhere. Learning it and working with it is a given. Back then, having access to a unix system was not a given. It was very expensive for hardware and software. The idea that one would be so close to the system and could be denied enough access by an overzealous BOFH was too much to take.

It just goes to show that circumstances change, and things can get weird if we don't change with it.
I like the design, but the UX for dragging doesn't work that well for me, many times the dragged item gets "stuck" with no real feedback why, and sometimes it skips/jumps to the mouse location.
LimeSurvey 6
In the midwest there's no water shortage (the Mississippi and Missouri are not going to get exhausted), but it's relatively expensive, for now, to pipe that water onto corn to protect against a drought every 1 of 5 years.
Hacker gets in, exfiltrates your log files that mistakenly have session tokens in them, goes through over the course of an hour or two before stumbling upon an admin session token that's still valid apparently.

Could easily write a script to find the session tokens and check them for validity. Many have their TTLs directly embedded, no need to touch a server to check, at least for that.
Breast cancer is too common in women to be able to deduce this kind of stuff without a huge amount of data (if ever).

There are a few generic factors that are clearly causatively linked, but that doesn't mean we could work out less strong, or rarer links.

Whole genome sequencing is becoming more common as is immunological and genetic studies on cancer cells.

We might know one day but probably not any time soon.
You forgot the mandatory MSFT accounts to sign in with no way around last I checked (a few months ago).
I'd like to ask a question if I may, how can you get excited about a culture that asks to ask?
> It's disappointed in the past partly because it's slow and expensive because you have to pay human drivers.

The first PRT system was (and still is!) completely automated.
By not building a thinned array, presumably. They have 10^8 elements.
It's telling to me that I can't tell from your reframing which side is which.

From my experience, I would assume the one not considering the other person is the one in guess culture, assuming the other person can and ought to read their mind, and the one trying not to impose is the one who actually asks the other person for their opinion or consent, but I can equally see it the other way around, and think the opposite might actually be how you meant it.
Funny enough their guesses are backed by recent studies.
iOS and Android aren't 30 years old, so that's not possible. Assuming you get by signing/appstore/etc, I don't think you can take a compiled app from early iOS and run it on an iPhone now; Apple removes old apis and there's the whole 64-bit transition too.

Google isn't as aggressive and most? apps are bytecode only, but I kind of don't expect an apk for Android 1.0 to function properly if run on an Android today. At least if it does anything advanced with networking or needs permissions that changed a lot.

Linux should work if it was static compiled, and probably helps if it doesn't use audio; because Linux audio has changed a lot in 30 years. A dynamically linked Linux binary from 30 years ago is nearly hopeless, because it would have been linked against a different libc that's in common use today, and I doubt that will be on your system today. If you had the full filesystem, it should run in a chroot.

MacOS was System 7 in 1993, on 68k, not power pc. Those applications aren't running on your M2 without emulation. Dropping 32-bit support doesn't help either, of course.

FreeBSD 1.0 was released in November 1993, so it's not quite 30 years old, but I suspect a static compiled app may work, but libraries will be hard. FreeBSD makes compat packages to get libraries to run older software, but I don't see one for 1.x or 2.x, the package for 3.x was marked expired in 2010, but compat4x seems alive and well; that gets you 20 years of probable compatability.
That would be a very good argument against the further deployment of coal.
Anything that implements or consumes `io.Reader` or `io.Writer` would dispute that.
You've put it clearly and simply better than I managed in my reply. The data is just too noisy we will need extraordinary large datasets to even beging to make comments.
I didn’t say it prevented inflation, I said inflation was mild given the amount of stimulus. IMO this is because as supply of money increased demand did too, and supply was sufficient to meet demand and the economy expanded rather than price inflation.
Nobody's "panties are in a twist," as you so eloquently conjectured.

Many of America's alcohol-related regulations are, literally, Puritan in origin and exist largely due to historical precedent. [1] [2]

Thus, when encountering a surprisingly harsh anti-alcohol regulation, it's reasonable to question its origin and validity.

[1] https://en.wikipedia.org/wiki/Blue_laws_in_the_United_States
[2] https://www.etymonline.com/word/blue%20laws
It’s fascinating how one man can so finely hone his ability to be insufferable. Even if he’s right, his style and overconfidence are incredibly off-putting to me.
Hah! I was going to post this myself.

When he overlaid the gray boxes over the tracks I thought “that’s a VI!”.

I’d like to point that LabVIEW is not doing any of the fancy type stuff explained here (Either, Maybe, etc). It’s just that VIs (or functions in common parlance) can have multiple inputs and outputs, and LabVIEW’s graphical approach lends itself well to this use case. But LabVIEW’s type system is fairly primitive.
Disagree.

Usually you don't need to just know if there is an error or not -- sometimes you need to know what that error is. For example, an I/O error versus your image-is-too-small error -- you need to respond to the user differently. I've seen plenty of web apps that treat I/O errors and user input errors as a generic "an error happened" and that is completely wrong. Proper exception bubbling means none of that code that encounters the errors needs to necessarily know how to handle the error and your app always responds correctly.

That said, I don't use exceptions as much in JS because exception handling in JS is still very nascent. There's no base library of exceptions and telling different exceptions apart is not built-in to the language. In a language with more mature exception handling, it's a breeze.
I love micro for having mouse mode by default.

I use it to debug containers and short-lived VMs, because it’s easier to copy/paste stuff than configuring neovim (which I would normally use).

However! “Help” doesn’t start with G. That’s a bit weird. And someone mentioned ctrl-c. That’s a bit weird too ;)
> It’s good to obey the law. I certainly try. But treating it as some kind of holy grail of ethics is fraught with peril. You’re outsourcing your thinking to the lowest common denominator: it’s what people in positions of power feel is justice. Sometimes it is. Sometimes it isn’t. And when it isn’t, do you really want to be the kind of person that believes it should be obeyed no matter the tradeoffs?

Nice, so we should be allowed to break the law if we feel that something is not right?

Yes, laws may be unethical or immoral. There is a system in place to change them, though, at least in a democratic government. Self-driving cars are allowed to be in the streets because laws have changed. AirBnB is allowed to operate because the laws have changed. And I would rather have that, a slow process of adaptation, than a random guy letting their crazy inventions roam free just because he feels like he's "right".
Agreed. Nano use is somewhat of a red flag to me.

It’s SO inefficient in comparison to Vim, VSCode, or tons of other alternatives.

If it’s the only thing on the box, fine, but in reality usually Vim is the only editor installed.
We’ve got some regional variation in the US, maybe this could be one thing that varies?

New Englanders are famously less-chatty, but also quite direct, so I’m not sure exactly how to map it to this ask/guess thing. I think specifically the Yankee subculture tends toward guess.
My answer was poor but this is what you want
https://beef2live.com/story-beef-exports-country-year-date-0....

China hlused to be number 1 but they've been reducing their meat purchases since the late 2010s for obvious reasons.
Whenever I see a picture of a keyboard online I wish they would also publish a video of somebody actually using it.
It’s time for Americans to embrace small cars
It's true that MSG content in e.g. aged parmesan is high... but it's not so low in e.g. cheddar and people tend to use a lot more of that.

Also mushrooms, tomatoes, etc. especially dried.

Mainly staying away from too much processed foods helps, but MSG content isnt' the main problem with them, it's a combination of flavoring agents + very high calorie density.
I don't think you can make many country-wide generalizations about this. My experience is that it varies widely by:

* Region

* Socioeconomic status

* Invidual psychology

The strongest "ask culture" people I've seen are poor people with good self esteem who grew up in historically poor areas like the South and stayed there. These people have a natural sense of "we have to take care of each other", a long-term commitment to their community, and an automatic understanding that they have helped many others before and thus deserve help in return.

The strongest "guess culture" people I've seen are wealthy insecure people that have moved around a bunch. They are financially secure enough to not need help most of the time, and expect others to also take care of themselves. They don't have the kind of long-term roots that make reciprocity feel natural. At the same time, they do want connection and community, so they work hard to try to understand the implicit needs and desires of the other guess culture people around them so that they can be helpful.

I'm definitely very far onto the guess culture side, but I know that I would be healthier if I could be more ask culture.
Particularly the way coleslaw is presented in the US. You can make a perfectly delicious and healthful coleslaw without mayonnaise or cream (or sugar!)

I just looked at the ingredients of a premade coleslaw (Safeway). The second and third ingredients are mayonnaise and sugar respectively.
Glad to see the EFF back on mission instead of dumb shit like spreading FUD to help keep their lawyer friends in the Library of Congress unaccountable to the rest of government.
The thing that gets me about self-driving vehicles is they just stop and block the road when they're confused (unsolvable situation, network disconnect, etc.) We can snicker at Cruise's meltdown during Outside Lands, but I keep thinking of the videos of people driving out of the Paradise fire, or more recently the Maui fire. One confused vehicle could kill dozens, hundreds, even thousands of people behind it.
In languages with a Result type (or Either monad), you basically do have checked exceptions, even though the language has no exceptions.
It's definitely bad in a work context where clear and effective communication is important.

You're probably thinking "but implicit communication is just as effective!" but it definitely isn't. It's all about hints and guessing motivations which is inevitably unreliable.
Specifically you can't run a.out binaries anymore and ELF came about in 98.

So that's a pretty hard limit. Linux can run binaries that were compiled to the latest binary standard in 98.
You're clearly a Guess :)
What is special about the 'wheel' group and what is su even "checking" in the first place?

Users who aren't in the wheel group aren't supposed to be able to become root, even if they have the password.

Isn't it just supposed to switch user? And what are the implications of not-checking whatever it was supposed to check?

Someone who steals the root password (say, by looking over the sysadmin's shoulder) would be able to become root.

And I also don't get: if someone has the root password, can't they change what groups they're a member of?

No, because they can't log in as root and (on non-broken systems) can't become root.
https://www.nytimes.com/2022/11/27/opinion/environment/missi...

> Last month, record low water levels in the Mississippi River backed up nearly 3,000 barges — the equivalent of 210,000 container trucks — on America’s most important inland waterway. Despite frantic dredging, farmers could move only half the corn they’d shipped the same time last year. Deliveries of fuel, coal, industrial chemicals and building materials were similarly delayed throughout the nation’s heartland.

> This critical river and its tributaries — responsible for transporting more than $17 billion worth of farm products and 60 percent of all U.S. corn and soybean exports annually — has been stricken by drought since September, amid a time of global grain shortage and soaring food prices. While water levels will recover modestly this week, thanks to some upstream rain and snow, the long-term forecast remains dry.
In Go, you can attach methods to functions (and any type really, even "unboxed" primitives).

One of the canonical examples would be a net/http: A handler can both be a struct (or any other type really) that implements a serve method, or it can be a handler function that calls itself to satisfy the interface.

In Clojure you would achieve the thing you describe by attaching metadata on your function var. It being a Lisp, it also has macros so you can pretty much do anything.

Speaking of macros:

Clojure also implements CSP channels with macros in core/async, inspired by Go.

Channels are a very powerful construct that you might like a lot. With channels you can completely avoid the function coloring problem (callbacks, promises, async/await). Perhaps most importantly they decouple execution from communication.

So going back to your example, your commands could be producers that send their results on channels. They don't need to know what consumes w/e they make, nor do they need to hold on to it, mutate something, or call something directly.

Good analogies would be buses on motherboards, routers and switches in networks, conveyor belts, message queues in distributed systems and so on.
> It reminds me of something I'd read that one of the reasons modern capitalism is so borked is because the founding fathers weren't conceiving of things like "Amazon" existing, where one entity employs a staggeringly large number of employees. Or that a small number of companies would employ such a large percentage of workers.

I'm not quite sure I buy that argument. They lived in the time of the East India Company, which owned something like 50% of the world's trade at the time and ruled several nations.
The visibility looks fine to me, and you should also be able to hear it.
That's been done:

https://www.cdc.gov/niosh/topics/aircrew/cancer.html
Ever been to a medical provider (MD, NP, PA) and have them breeze in, mumble some questions to you, type some things on their computer while barely looking at you, and then breeze back out, all within 15 minutes?

That's because they are required to see as many patients as possible. One company my wife worked for required her to see 21 a day. She had bonuses tied to increased volume. Not their improved health outcomes. How many patients she saw.

Having bonuses tied to the number of patients she saw was something she experienced at every company she has worked for as an NP except one.

Now, tell me again how companies don't see patients as profit centers.

I agree with you that investors surely do. However, all but one of those companies she worked for were private companies--one was a family-owned practice.
I think it's the rise of transported from afar cheap vegetables. Since they are more sturdy, they are cheaper, it's more lucrative (and budget friendly when cooking at home) to get bland supermarket tomatoes and make a salad with them, by adding sauce.

Locally sourced vegetables can be much more flavourful, reducing the need for additional sauces. I always enjoy making a "tomato, cucumber, olive oil" salad and watch foreigners coming to Bulgaria ask "oh wow what sauce did you use" and I go - none, that's how those veggies are supposed to taste.

But you only get those kind of supplies by going to a bazaar/market and pick them out individually yourself.
> This category of exploit is prevented by credential rotation

This category of exploit is prevented in a huge number of ways - not a single one of them is "make my user's cookie/token sessions 15 minutes long"
You make some excellent points. Unfortunately most hardware at some point ends up in this state.
Yes, Unix was designed to protect users from each other but the modern need is to protect applications/invocations from each other. It is unfortunate that Unix wasn't really designed for the modern use case.

Basically https://xkcd.com/1200/
Is this Windows 11? On 10 Pro you were just able to click past it. Need it for office though, I think.
Why do people reblog old tropw essays, and why do they get upvoted?

Such a waste of energy to prop up someone's attempt to build a personal brand.

Cite your sources and contribute something new, or just share the more original link.
Last time I checked you could log in locally if the install process never detected an internet connection. A terrible work around but (at the time) a functional one.
You might like x!
You can disable direct root login and force users to login as their own account first. This way, any root login is tracked—you know who logged in as root, because they had to log in as their own account in order to run su.
I've worked on a few systems that were stored procedure heavy with Microsoft SQL server, not so much because I am a .NET guy, some of these came when I was working on super-random projects for a consulting company.

My take is that it is a lot like building a system that has an API over the database except that instead of writing in API in, say, Java and exposing it through an http API with, say, JAX-RS, you are writing the API in stored procedures and accessing it through JDBC or ODBC or the native API of the database.

It seems very possible to build some thin layer that uses metadata to make an http API over stored procedures.

I'd say that systems like that can work very well.

The basic challenge is maintaining version control over your scripts, my coworkers were rubyists on my first such project and built a system inspired by migrations in Ruby on Rails where we wrote up and down migration scripts for every database change. I carried that approach to other projects where the people had less discipline to begin with. There is a little awkwardness there that the "down" script that reverts a procedure to a previous version has a cut-and-pasted copy of the old version of the stored procedure, if I had to do it over again I'd make something where each version of a stored proc is in a numbered file and the "migrations" just say "upgrade ABC proc to version 7" or maybe you could make something that looks into the VCS and finds the old version.

From what I've read, PL/SQL from Oracle looks a lot better than the Transact-SQL language in SQL server but I've never done a major project with Oracle. Most places I've worked at recently use PostgreSQL and I think this would be a viable architecture for that.

One area where it seems to be a hassle is with the "query builder" pattern, for instance where I work now we have a very complex search form with a huge number of options that builds a SQL query. I think you can do that kind of thing with what they call "Dynamic SQL", see

https://www.postgresql.org/docs/15/plpgsql-statements.html#P...

but it seems preferable to do that kind of thing with a real programming language, particularly if you have tools like

https://www.jooq.org/
Yeah, to bad we don't record employment records. Oh well.
If you look at the history of what is considered a safe dosage of radiation you'll notice the amount only ever goes down, never up.
> But US states can't regulate interstate commerce.

This is wrong: so long as it is neither discriminating against interstate trade (that is, as long as it treats interstate and in-state trade equally), nor acting in areas where Congress has explicitly or implicitly, by adopting its own regulations, prohibited state action, yes, they can.

And while the FCC anti-neutrality regulation was asserted in court to preempt state action, that arguement failed to prevail.
Using this style is infectious like any other monad, so all your business will look like this.
Stop reading if you are ok with this.

That said, let's talk about validation errors vs. exceptions.

Exceptions are - as the name implies - unexpected errors that unwind the stack to whoever catches them. Along the way any necessary cleanup is handled automatically.

Exceptions are for cases where the error occurring is outside the scope of the business function.
I/O errors come to mind, OOM etc.

Now if you want to VALIDATE your data, you can do this without resorting to exception handlers or monads: You turn the outcome to your functional pipeline into data.
Have validation errors? collect them in a set. Look at them after the pipeline completes.
Chances are you don't want to fail on the first one.

Need to do side-effects in a pipeline? Don't. Instead describe the effect with data, run them later.

Need to back out early out of the pipeline? Split the pipeline at that location, handle the result, stuff it into another pipeline.

Or use (shudder) a chain of interceptors that can decide if the pipeline should be continued along its happy path. If your language supports it, use pattern matching to make that decision. Note that the decision making to skip parts of the pipeline or the rest of it, is done outside your business function (which improves the chances of them being reusable because they will only be concerned with a pure data transformation and don't need to know about machinations like Maybe/Either or some such to signal things to the caller).
That's assuming your sale is the only data they have about the value of your assets. But real estate sales happen all the time.

Now, if everybody is selling every building at a large discount, that's a housing crash, and highly-leveraged real estate companies are toast. But that should only happen if there is a real estate bubble, in which case a market correction is ultimately necessary and the entities that buy at the peak of the market are supposed to lose their shirts.

What you want to do in that case is not to save them. They're done. What you want is to prevent a cascading failure into the rest of the economy.
What term would you use to describe it? Respectfully, I think you're projecting an opinion onto it. There's no inherent value in the word "Guess". A "guess" culture isn't without transactional interactions, it's just shifted the transaction to implicit expectations instead of explicit.
It's a bit surprising that there isn't a project that takes the old Windows "shell replacement" (LiteStep, etc) idea a bit further and replaces the majority of the Windows userland. That's probably more challenging now than it was in the XP-Vista-7 days but should still be doable.
The latest job-hunting tool: dating apps
Might be the dawning of the age of aquarius. Not really enough evidence in any direction right now.
https://www.onemodel.org aka OM: available and in daily use, but progress is slow until health improves. A highly effective (desktop) knowledge manager, text UI, Free (AGPL), using Scala and PostgreSQL (working to move to Rust). Something like an efficient combination of mindmap, zettelkasten and GTD in one, with much greater ambitions including for linking instances for collaboration; see site links to screen shots for some idea of how I organize/categorize things. Low-volume announcements email list available (under "community").
Exploring EXIF
Nano is not a powerful text editor and is generally only used by non sophisticated users.