skysight-inc/HackerNews huggingface dataset:
Part of Julius Caesar's tyranny was his work to cancel the debt of common people and redistribute land- Debt owed to wealthy (the senate), and land 'owned' (seized from the public) by the wealthy (the senate).

Depending on what aspects of history you learned, there could be good reason to put a flower on his grave.

https://www.jstor.org/stable/292075

here's a bit on Lex Agraria, though focused on the earlier one from Tiberius https://www.britannica.com/topic/land-reform/History-of-land...
Yes.

But the power company (be it government owned or private) is at a "commanding height". It is almost impossible to exist without their service so they have very large social responsibilities. Far larger than the responsibility to their shareholders.
Can you please expand on this? Is any of your comment explained by pointing that many European countries have shuttered nuclear plants, which presumably has led to increased energy prices but unrelated to the focus on renewables?
For reasons the above commenter has already mentioned.

Most founder either want to run a profitable business or make their way to a big exit. Company valued at 10b? Great, sell or IPO. If the founder really realized that there was no profit ever to be made and genuinely didnt believe in the future of the company then the best move for their own self-interest would be to sell and gtfo.

Not only if your premise impractical, but it's inherently illogical for your antagonist to act as you imagine.
Thank you! Yes, we intend to expand filtering with time. Thank you for the suggestion.
It tickles my funny bone to no end that William of Orange is known to the Spaniards as Guillermo de Naranja.

It shouldn't, somehow, Guillermo is William and Naranja is orang, it just sounds like someone is having me on.
That's a nice way of saying "Deliberate hardware incompatibility", when those modules look pretty clearly to be MSATA in form-factor.
This is awesome and congrats on going live! I'ave had similar problems.
As an example, this sign [1] is at the edge of Copenhagen's main pedestrian shopping street.

The international symbols show it's a pedestrian zone, and there's a rule of no stopping from 11-04 (no stopping meaning not even any loading/unloading, a stronger restriction than no parking.)

The text says "Residents excepted" (under the graffiti/sticker) and "Goods vehicles excepted 04-11" (so deliveries and rubbish collection in the morning) on all days including Sundays and public holidays.

50m down the cross-street on which the StreetView car is driving, there's the standard sign for no motor vehicles [2], and the text underneath says "Except for business" -- so this street can be used all day for delivery vehicles etc.

Both signs are enforced similar to parking: get caught, and you'll be fined. I'm sure you're less likely to be challenged if you're driving a van with "Plumber" written on the side, but it shouldn't matter.

No doubt it's more complicated in cities where this is enforced by cameras.

(In addition, the pedestrian streets are mostly conflicting one-way streets [3, and do a 360°]. No problem for a delivery, but useless as a shortcut.)

[1] https://www.google.com/maps/@55.6779772,12.5729422,3a,25.5y,...

[2] https://www.google.com/maps/@55.6772541,12.5737765,3a,23.2y,...

[3] https://www.google.com/maps/@55.6814522,12.5751944,3a,75y,12...
Religion-Fueled Mobs on the Rise Again in Pakistan
Heat pumps are useless in hard frost.

The one I own stops being useful at 3 degrees of frost, struggles before then
Battery life seems to be the biggest thing holding it back from a daily driver for myself.

Afternoon to 10pm with light use, so around 8 hours. Would be curious to see how long it last with maps and music going.
I think it's well-designed, but I would definitely want someone to go over it and look for any obvious issues if I made it public. I wanted it to be annoying as possible to do something outside of the tenant context and it is definitely annoying. Absent an explicit flag to disable tenancy for a specific operation, the operation will fail, raising an exception that the tenant id was not set. This is mostly enforced at the database interface right now i.e. the interface ensures that a tenant id is present in the query. Then in the database itself, null values for the tenant id aren't allowed. I also have a test that runs over every table and ensures there is a tenant id column except for those that are explicitly listed in the test as not needing a tenant id. I also have it set up to not expose the tenant id to the user at all, instead opting for a "public id" with limited utility and only used where needed.
Some machines are configured by the devil himself.
Bored Ape Yacht Club pitch deck
Russia wants to put Germany in a bad negotiation position. If internal pressure to shutdown Russian gas becomes too strong, and shutting down Russian gas is a tremendous self-inflicted harm, a better alternative for politicians is to find a quick compromise with Russia.

Without russia having to publicly force this to happen.
What should the expectation of useful life of an EV be? My family's daily drivers are 2007 Honda models, both w/ >200K miles and can still achieve 100% of their factory-new range, don't burn oil, and pass emissions and safety checks. I don't think a 15 year operational lifetime for a modern vehicle is at all unreasonable.
I wonder if there’s a simpler explanation: that it’s easier to be dispassionate and deprioritise attractiveness for other people?

If I was advising a friend, my head would rule: I’d tell them that while attractiveness is nice to have, they should prioritise other aspects (values, temperament, etc.) in choosing someone to be happy with in the long term. I have no vested interest in how attractive my friend’s partner is - only in their happiness.

But when making a choice for myself, heart (or raging hormones?) plays a much bigger role, and attractiveness is prioritised much higher, especially at first. And I do (obviously) have a vested interest in optimising for the attractiveness of my partner, all else being equal.
I thought that only Bulgarian producers have been doing these dirty tricks - I've seen brands having up to 70% of palm oil! I don't know how is this even allowed - to abuse the meaning of "butter"! Call it something else and put whatever you wish in it, but often people buy assuming what butter actually means and dont' read the ingredients.
OK. It's a snowstorm. Would you rather spin out in something that weighs 4000lbs or something that is more like an enclosed ATV or a gator with studded tires? The physics is on your side with the smaller and lighter vehicle plus of course the efficiency gains to be had from requiring less energy overall to go the same distance since your total weight is going to be lower.
Adding Akamai Shared Domains to the Public Suffix List
Prepositions are the bane of getting true fluency in English. Making up and making out are both options, but very different ones.
I'd imagine anyone concerned about efficiancy at Ikea would just order online.

The value proposition of the long Ikea walks is the set up rooms showing how the products look in use, allowing you to visualise before you buy. I take a friend and a coffee and take my time at Ikea.
>The most obvious example is non-!important rules in user stylesheets.

You are fundamentally unable to force the user to render the text you send them in a particular font size, !important or not. What if they use a text browser and small font size in the terminal?

The legal requirement explanation makes 0 sense.
A lot of humour consists of buildup followed by a twist - the humour is in the contrast between the expected and the actual. This is very similar to explaining a concept that is flawed or misunderstood by building up a scenario where the expected outcome can be contrasted with an actual outcome. A smaller set replaces 'actual' with 'nonsense'.

The text may present this as wisdom, but I would say it is both wisdom and humour.
They didn't say it causes the complexity, just that React hides a lot of complexity away. React is very simple and easy to use on it's surface, but it an incredibly complex collection of software under the hood.
> No one's stopping you from emptying your savings account and giving all your money to people who would derive orders of magnitude more utility from it than you.

That is an unhelpful comment and an antisocial position. (And as another commentator put it "a tax on empathy")

Humans are social creatures, we cannot survive on our own.

We are also monkeys with enormous brains, we can do better
I think the complexity claims for microservices are way overblown. There are a set of trade offs to be made on both microservices and monoliths.

For microservices you need a good idea of how you’re going to do IPC and how you’re going to maintain isolated state. In most cases there are reasonably easy solutions to both problems, but in general there is a little bit more more up-front work to do when starting with microservices.

For monoliths you need a good understanding of how you are going to upgrade a running system without downtime, and how you are going to stop developers from taking stupid shortcuts that create invisible internal coupling. IMO, if your team is big enough to have the necessary processes to get this right, it’s big enough to deal with microservices too.

So I honestly don’t get the hate from some on HN for microservices. You can fuck anything up if you try hard enough, but microservices epitomise the principles of good systems engineering, most particularly around separation of concerns. I honestly don’t understand why anyone would choose a monolithic architecture for a new build in 2022.
>but if you want to rewrite the codebase into a different paradigm you need to clearly demonstrate what we'll be getting out of it.

Well, that all seems reasonable until that upstart competitor comes along and upends the market with simpler stuff that doesn’t require so much bondage and discipline and tithe to process religion suppliers, and the customers start to question the value you’re supplying and wham, all that orderly process and framing is like out the window, man, like man the lifeboats. It’s a pain to stay in the game when it seems like change for changes’ sake and there’s no time to sit down and reason through a business case before the next new shiny hits. Stupid but true.

I still remember Digital trying to sell me maintenance contracts for 20 year old PDP-11s still in service out in the field. We rebuilt our entire infrastructure from scratch on new software and hardware in less than a year for 2/3rds the cost of the annual maintenance contract...the next year those pretty wood paneled Digital offices with executive dining rooms had "for lease" signs out front. Digital had failed the paradigm shift.
State wasn't evil, the lifecycle callbacks were. I don't think they ever deprecated setState, but I'm pretty sure they've nudged people away from the lifecycles..

Class components when needing more complex behaviours related to lifecycles/context had the choice of:

a. Hard wiring up all the different lifecycle events to bespoke systems, on a per component basis (use same thing in 5 places? Implement it 5 times)

b. export const ActualWorkingComponent = HOC(HOC(HOC(HOC(NonWorkingWithoutHocComponent,{conf4}),{conf1}),{conf2}),{conf3});

I will fully admit that useState is more aimed at singular/simple values, so a more complex object is a pain to directly copy over. (useReducer or wrapping setState could work, as the child components shouldn't re-render unless their props change).

But it is so much nicer to have the dependencies at the start of the the functional component, and not in a horrid callstack at the bottom, with 3 different ways of defining which prop gets which HOC's values/functions and then injecting even more callbacks to munge those values from the out HOCs to use in that HOC to make it's output good for next HOC...

Instead, it's just:

const {widgetId} = useRouterParams();
const widgetData = useSelector(selectWidgetById(widgetId));

No mess, no fuss, use it it in a few places? Wrap it up in a function of it's own.
There are so many local and indie artists who are willing to give you their work for free and would be thrilled to see you copying it to your friends. Those are the people who care about the free flow of information the most. They're also usually the ones who respect the intentions of creators the most. Because if you won't agree to pay money for it and be forbidden from copying, then the smart thing to do isn't to pull out bittorrent. The smart thing to do instead, is pull out your guitar and start recording something better. That's what freedom is. Maybe if everyone wasn't so focused on pirating Goliath, more people would be supporting David.
We found extensions like Honey to be invasive, so we designed ours to be low profile. It will alert you only when we've found item elsewhere. Right now, this is around 200,000 products.
It’s cheapness and greed on the boss’s part.
I think that one has to separate out architecture and implementation a bit, they're obviously a deeply intertwingled dance - but you have to start with the architecture and tweak from there to get the best result in the end - I'm probably halfway through that process now, starting to introduce deeper timing constraints to flesh out that stuff

BTW once great thing that sort of falls out of this architecture is that the commit register file gets shared between the integer and FP registers (and probably vector registers too), and duping just that may be an interesting architectural way to go
I find the organizational arguments to be pretty convincing, but surely there must be a way to reap these rewards in a monolithic infra setup as well? Maybe someone should develop a "monolith microservice architecture" where all the services are essentially (and enforced to be) isolated, but once deployed is built like a single unit.

You could do it with docker-compose I guess, but optimally your end result would be a single portable application.
Is this generally the case? If so, I had no idea...
You can make the qualifiers less silly looking by matching the qualifier you're trying to override exactly. This makes it more obvious what exactly it is that you are overriding, and has the added benefit of only applying in that one place.

If you explicitly want to change one element in every place, though, !important comes in handy.
Why would you need useMemo in a class component? You can just attach a memoized instance of the function to the component
I’m sure they are right but it’s amusing in that government is the biggest abuser of this sort of thing.
> The goal of increased interest rates is to make borrowing more expensive, which means business and consumers would cut down on investment or loans, since those are good mechanisms for money creation. It slows the velocity of money and therefore demand.

And the business that don't get as easy credit will not hire as many people. Let's not hide behind the abstractions that exact causal mechanism here.

It's usually the same barely employed marginalized folks that are "last to higher, first to fire" too. This is empirically established.

Some service workers loose my job, but stupid investment still pours into blockchain bullshit? What a crude lever this monetary policy is!

It would be much better to adopt some new more precise levers. For example, the rules on the collateral for loans could be changed to pop a bubble. Or Gasoline prices should go up way more (with a new UBI to compensate) to encourage rationing of that key thing while not effecting demand overall.

Basically, the policy should match the underlying cause in the supply shocks. Treating all inflations as all the same is crude and punishes poor people extra for no justifiable reason.
How is a legal requirement different to a business requirement? Both need to be satisfied.
Compute Cloud Independence by Wasabi and Vultr
This Russian gas dependency was solidified well into Russian recent developments. After Crimea invasion, as an example. After Russian influence over American election.
Hmm. Interesting. I would like to try it on the Raspberry pi 400..

It also looks like you need to purchase the amiga os & ROMS separately.
If anyone is curious about how this started, Asianometry (a favorite channel of mine) has a video about how Gogoro built their network in Taiwan

https://youtu.be/xZigLuaijsI
Had to look up Datavision D-3000 in action.
https://www.youtube.com/watch?v=tt-gN-cIpxs
Crazy!
Conversely at my local supermarket (major chain), the milk, meat, fruit and veg are all near the front of the store and easily accessible.

Also, why would your eggs be in the dairy section?
> macOS is known to be slow. If someone has Asahi running and wants some karma, try running lmbench and post the results.

Clarification required: slow by lmbench or what measure?

In my (personal, anecdotal) experience macOS is more responsive – with fewer UI hiccups – than Ubuntu on the same hardware (== faster!) but takes a lot longer to boot up (== slower!).
I don’t know if it’s illegal, but basically every health care plan will deny you if they know you have other coverage. This is bad advice.
Time since 2015 is rather more than a year. And, all appearances are that any signatory no longer exists, as such.

Finally, if you don't yet know about voluntary termination of contracts, you have an opportunity to learn more about it.
Cities can solve this by enforcing geofencing to only allow locking the scooter in designated areas. Santa Monica for example paints scooter parking spots on a lot of street corners that would otherwise be pretty littered.
As another comment pointed out this was the case long before the civil war (which started in 1861 and I was saying you could see this in the GDP difference even in 1800
I did the same some 10 years ago only to discover I'm too lazy to do post-processing on my timelapse.
You can definitely use it to record successions of stills and videos which I guess is part of what phones do. It would be better if there was native firmware support for some of that stuff though, and I imagine that some combination of firmware acquisition settings and accelerometer data would give you the same capabilities as smartphones. Perhaps maybe a secondary camera with a high framerate to get optical flow/camera pose data from? Dunno.

You can still do it manually, but give it 3 years and you'll be able to compose that photo from scratch with an off-the-shelf generative NN photoshop plugin anyway.
But still I'd say the market for DSLRs will remain the same because their main function (in my opinion) is to capture an accurate representation of reality with predictable errors in pixel space and not in some latent one.
> if Ukraine was a thorn in the Kremlin's side

If Ukraine was THE thorn in the Kremlin's side... vs one point in a constellation of concerns including undermining NATO [0], weakening the EU [1], weakening the US, affirming nationalist authoritarianism vs social democracy, etc etc.

> it would have been rational for Russia to stabilize the issue with an invasion

If invasions didn't have any risks and consequences (even absent US intervention). And at this point, it sure looks like those risks and consequences are on full display even if we only look at the military action.

Meanwhile 3 years ago it actually looked plausible that the US could be forced into having to sacrifice either aid to Ukraine or the candidate that eventually beat Trump.

> discredited media stories notwithstanding.

"discredited" needs citation. Especially considering that the introductory set of articles I linked to above isn't even the short list.

[0] https://www.nytimes.com/2020/09/03/us/politics/trump-nato-wi...
[1] https://france-amerique.com/en/trump-has-done-everything-he-...
It's not about manipulation, but manners. Where I live, you literally do ask, "Is this the final price?" Or a lengthier way might be, "This is a beautiful thing and I would love to have it! But alas, it is beyond my budget."

Most cultures are not as direct as American. In the US, it's a virtue to save time instead of dancing around the question. But in some cultures, dancing around the question is a mark of respect. You first acknowledge that the seller has been generous and then ask them for further generosity.
I would be fine with this, but the job would have to pay at least the consumer market cost of healthcare plus plenty of headroom for increases more than the next best offer for me to consider it.
I believe this to be reasonable, though I believe there's an even stronger force at play: engineering retention. In other words, let engineers build whatever they want to build, within reason of course, because if they don't they may just go to another company that will let them. Solving for boredom. Complex systems are interesting.

I'm going to flip the narrative a little bit: whether its "tech is the end-game" or "engineers are bored and just want to have fun", I'm not sure I see the problem. I've grown out of the "maximally efficient business is the endgame" propaganda. My endgame at work is to have fun and produce enough value so I can come back tomorrow and continue having fun. Business as the endgame is a great motive for the CEOs who make millions a year. I'm not that.

Put another way, many people say that coding is as much art as science or engineering. Artists may do commissions, but ultimately their work comes from within; its not by-and-large prescriptive. The endgame is the art; the endgame is the tech; and, hopefully, that endgame is marketable. Sometimes it is, sometimes it isn't; that's not especially relevant to the process.

Or, you can take the stance that the endgame is the business, and spend your life unfulfilled, making your rich boss richer. I'd rather seek fulfillment from the tech; not the money.
The "do one thing and do it well" Unix philosophy already broke down decades ago when people started adding things like "cat -v" and ability to sort ls and whatnot. People like Doug McIlroy still argue that's all "useless bloat". Pretty much the entire rest of the world disagrees. The point is that "do one thing and do it well" doesn't actually work all that well in reality.

A CLI not a service: there is no operational complexity to "keep things running" in a CLI: you just chain some things together with pipes and that's that. The nice thing about that is that the text interface is generic and you can do things the original authors never thought of. With microservices this usually isn't the case and things are extremely specific. This is also why "do one thing and do it well" doesn't really carry over very well to GUIs.

A lot of microservices I've seen are just functions calls, but with the extra steps of the network stack, gRPC, etc. Some would argue that this is "doing microservices wrong" – and I'd agree – but the reality of the matter is that this is how most people are actually using microservices, and that this is what microservices mean to many people today.

Instead of "microservices" we need to think about "event-driven logic", or something like that. Currently the industry is absolutely obsessed with how you run things, rather than how you design things.
Our hubris knows no bounds
They sure like their email at Google. At most other organizations, sensitive email chains would be open to discovery but would just end by saying "call me" :)
It seems a little bad-faith of the article to relegate to a footnote at the bottom their admission that the practice they're complaining about was changed three days before their article was written.
The reason for choosing monolithic architecture is simple: velocity. You need to move fast and be nimble until you are able to find a product that people want and/or need to use.

The people who (at least initially) advocated for microservices were the first to point out that it is better to start as a monolith and then refactor into microservices as required by external factors.