skysight-inc/HackerNews huggingface dataset:
The TL;DR is there isn't much difference besides the protocol being used. Tailscale published their own comparison that seems pretty fair to both sides (they do this for a few other options as well) https://tailscale.com/compare/zerotier.
That suggestion that people buy iPhones merely because of iMessage is outrageous to a non-American. While I might certainly be one of the reasons, I doubt it’s the reason, unless the user is 12.
>if there's consensus then bad laws can be changed, or good ones extended, or the filibuster removed, etc. so why have them auto-expire anyway?

The auto-expire thing is a good idea; it's basically automatic garbage collecting. It's a procedure which forces the legislature to review every old law to see if it needs updating or renewal or not. Many laws are old and forgotten, because the legislature isn't forced (by its own auto-expire procedure) to review these old laws, and then they eventually cause problems because some lawyer digs them up and applies them to a case.

The Patriot Act got extended without fuss because it had lots of bipartisan support. You may disagree with the Act, but almost all the congresspeople liked it (and they were elected or re-elected by the voters), so it's correct that it was extended.

If the EPA doesn't enjoy that level of support, or even enough support for Congress to re-authorize it every so often, then it should be abolished. Sure, that will result in disaster (burning rivers and the like), but if that's what the People want, that's what they should get, unless you think the government should be replaced with an authoritarian system.

You may think the EPA and environmental protection is important, but you share a country with a huge number of uneducated morons who don't, and their vote is just as valid as yours.
People have spent more than 5 minutes thinking about it. There's a 2018 book called Radical Markets[1] that explores alternative models for various entranced economic systems, such as property ownership, voting etc. There's a free podcast interview with the author online[2].

The tl;dr is that you'd decide what your $500k home is worth. You could choose to say it's worth $80k, $500k etc. You'd then pay property tax as a function of what you decided it's worth.

The catch is that you'd be obligated to sell it at the price you selected if a buyer showed up.

In economics lingo one thing you can optimize for is "investment efficiency", or "allocation efficiency". Traditional land ownership is the canonical example of the former, someone else might be able to make better use of your land ("allocation efficiency"), but they don't own it, so tough luck.

Turning all "land ownership" into what's basically a mandatory bidding system is a way of maximizing allocation efficiency, you'd optimize for (re)allocating land to someone who can most efficiently use it.

The authors spend a lot of time discussing the various edge cases, and in particular the normal knee-jerk responses someone might have.

In particular you can set a system like this up in such a way that a "mandatory buyout" would be a fantastic deal for a given homeowner, e.g. the equivalent of having someone offer you $1 million for your $500k house.

1. https://press.princeton.edu/books/hardcover/9780691177502/ra...

2. https://www.econtalk.org/glen-weyl-on-radical-markets/
Challenges in AIML Adoption in Enterprises
I'm probably biased because I live in firmware development these days, but that's true even for non-garbage collected languages when it comes to making sure things are fast
Frameless Browser for Screenshots
The right URL is: https://dheatattack.com
> I saw 95% perf at 60% of the power come up, ie 270w

That's neat, but 5% is a lot when you're spending $1600. Oh and all these measurements you see tossed around are done with air coolers and stock voltages. Of course more power doesn't help if you're limited by thermals. Specifically, you're limited by hotspots you can't see because they're between the on-die temperature sensors.

> maybe configure that as an optional profile for titles not needing maximum juice?

4K gsync monitors are typically limited to 120Hz. If my GPU is capable of running a title at 1200fps, it will idle 90% of the time and consume only ~60W regardless of the 600W power limit. So tuning this is pointless. I'd still get 1/10th the rendering latency compared to a GPU that's only capable of 120fps. Same logic applies to power limiting your GPU which will increase latency and kill frame pacing in exchange for a tiny reduction in electricity bills.
Yes, they should, but as they are evil they took the bigger and easier target.
This is frankly a disastrous impact to the usability of Observable notebooks for Free Individuals (the new free tier). From the FAQ (https://talk.observablehq.com/t/faq-october-2022-platform-ch...)

Q: With live public notebooks, is there a way to stage edits before making them public?
[...]
For Free users, we also recommend that they fork the notebook (which would be public), make the edits and merge the changes back.
Although the forked notebooks would be public, it would be a temporary notebook which could be deleted once merged.

So Free Individuals just have to... break their live notebooks if they want to edit them?

Like fine, kneecap your free product if you really need to force people to fork over cash. But Observable purports to be a platform that is trying to democratise data analysis and visualisation for the masses. Feels a bit like Wikipedia adding its own paid tier.
To be honest, Shopify isn’t particularly invested in Ruby concurrency.

That’s not really a use case we have, and the community is already investing a lot in that direction (ioquatix with fiber scheduler and ko1 with N:M threads and Ractors)
No shit, sherlock.

Instead of continuing the bickering, you could show us the code base, how 'bout that?
This is one of my hobby horses! I'm disclaiming my bias upfront so I can try and have empathy for your position, but I strongly disagree with this line of thinking. I've been thinking a lot about this personally, and I think I would summarize my argument as "a lot of engineers think they're building beautiful, bespoke palaces, but in truth they're building regular houses, which is actually more important in the macro, but should be boring in the micro".

I broadly agree with GP here, but to round out some of their points:

- Frameworks take care of the parts of your application that aren't special. In the same way garbage collection isn't the value your company provides to customers, HTTP header parsing (or whatever) isn't either.

- Frameworks prevent your team from diving down architecture rabbit holes, or having to read a bunch of books on DDD, or what have you. This sounds like a small point, but if you tracked the number of expensive engineering hours spent disagreeing about where code should go, look like, and work, you would realize it's a pretty big one.

- Frameworks are tested way better than you ever could by thousands of users, actually documented, contain compatibility guarantees, and have security policies. To match this quality, your company would probably spend millions of dollars on eng hours. That's why company-specific frameworks don't match this quality.

- Frameworks make onboarding way easier. Most Python engineers know Django; most Ruby engineers know Rails. By definition, you can't hire engineers that already know your framework (even if you use something like Hexagonal, because no two implementations of this are alike). And again, because your in-house framework will be poorly tested/documented/etc., new hires will struggle. They'll also wonder if this is a career cul-de-sac: "I have 4 years of irrelevant experience in [bespoke framework X]" is not an enticing resume bullet.

> Your software is custom made for your organisation, it's not mass producing identical systems on an assembly line

This returns us to the palace vs. suburbs framing. The software you write is a super small percentage of the code that runs your app, all the way from firmware to CSS libraries. Good engineering is carefully deciding what code you will write yourself, because code isn't just implementation, it's design, buy-in, maintenance, documentation, and liability. Some enterprises are replacing a big chunk of that stack (Oxide or Cloudflare come to mind), but I bet 95% of companies are just building REST/GraphQL servers. That's not special enough to require a custom, in-house framework. You should just build the house the regular way.
I use:

fc -l 1 | grep foo
For me (also northern Europe) it seems that everyone uses WhatsApp.
> IMHO that should also apply to land ownership rights which should also expire after some time.

Why limit ownership restrictions to land ownership only?

Private ownership of property (not limited to land) is foundational for functioning democracies; some would even go as far as saying it's foundational for society.

Those societies that went your route of "from each according to his abilities to each according to his need" turned out very badly.
> Gengis Khan is not my granddad

But he may be the "grandad" of many people! :-)

https://www.discovermagazine.com/the-sciences/1-in-200-men-d...
Thing is, companies aren't just a web of contracted individuals.

Companies gain efficiencies from reduced transaction costs; this is the basic theory of the firm, the reason we have firms at all.

One of the big ways transaction costs are reduced is by increased trust, trust at the human level. Interactions don't need lots of checks and guards and ass-covering because there's mutual trust, at a human level, that people are working together on a profit-making enterprise.

Breaking trust affects efficiency. If someone threatens to leave, you can't make future plans that assume they're in place. People aren't cogs that can be trivially replaced; on-the-job knowledge makes people more productive and takes time to acquire. So if someone's future presence is uncertain, timelines stretch, more people need to be allocated to it to account for risk of people leaving, and so on.

And this affects other trust relationships further out. A manager of a team or a product area may not be able to deliver on commitments that serve a strategic purpose of the company directed at a higher level.

It's not "purely business". Businesses run on trust; companies are collections of individuals with a higher degree of mutual trust, and the more trust they have, the more they can eliminate inefficiencies caused by lacking trust. That's why companies work at all.
I think he might just move to some civilised country from that sort of third world nation with kangaroo courts... Only sensible choice to do.
Hard for me to disagree with that. The reason I have an iPhone is that I was having trouble with the family group chat when my mom was in the hospital.
One thing I didn’t like about UO was the ability to travel instantly from one place to another through the use of runes.

I feel like if that feature had been removed, it would make locations and travel far more significant.

I remember sailing the seas with my boat and the sense of exploration I had by visiting islands few people had been to.

I also feel like there should have been consequences for logging out in the wilderness, perhaps a strong chance of waking up to some monster encounter and with less than half your HP when you log in. This would incentivize people to seek towns or homes or at least use the camping skill.

I think UO really shines when you lean into hardcore elements.
With framework maintainers providing paid support, extending services or an ecosystem with commercial components it somewhat makes sense even if not outright obvious or intentional.
Indeed. particularly good proof at how trivial it is to disperse misinformation. I note depending on the bias of that information it seems more likely to become pervasive.
And anyone who subsequently voted for them or gave them money. I think they all should pay couple hundred million to victims and then spend rest of their lives in prison.
How many of these users are actually people and not bots? Nobody will join a metaverse just to be surrounded by bots.
Or the counteroffer is to retain the person until the completion of an immediate project. It could be that the short-term loss of an individual exceeds the extra cost of a raise, but the long-term cost exceeds the benefits.

More likely, it's a case of non-generalizability. Profitable companies can normally afford to counter-offer in specific cases, but if the resulting raise became a rule in like-for-like employee relationships, the collective increase in payroll would not be affordable.
It requires active renewal which has implications. For example abandoned property is acquired by the state.
OK, sure, he's a fuckhead. He's a dumbass, he's a clown, he's not a smart man. He is an asshole.

But a billion dollars. A billion dollar judgment. You don't think they're rubbing his face in it a little? Teaching us all a lesson about what happens?
The article tries to generalize but I think it's a bad idea since not all frameworks are equal. Back in 2005 (and to this day), I made websites with Django and it was relatively easy to maintain and upgrade them to follow the framework. I can't say the same thing about websites I made using the Zend Framework (now Laminas).

The wrong framework will harm the maintenance of your software. The right framework will keep it going for decades.

Of course it's not always obvious how a framework will evolve over time (let alone the requirements of your website/app/api), so the safe bet is to stick with the ones that already stood the the test of time.
> The layoffs are happening in tech. Not as much elsewhere. This is .com bubble 2.0.

That's complete nonsense.

"The Automotive sector leads all industries in job cuts this year"

"Retailers led in job cut announcements in September"

"Technology companies followed"

Source: https://www.challengergray.com/blog/job-cuts-surge-46-in-sep...
> G(F) = “This sentence is not provable in F.”

> S(E) = “This sentence has no convincing heuristic explanation accepted by E.”

We can formalise in F what a proof is, but what is a "heuristic explanation"? So this doesn't really make much sense. This guy sounds like a physicist :-)
These are generally just resource issues. Companies generally won't pay for engineering hours to build really good framework documentation. It's not in the critical path. Companies that know that documentation, as well as tests, compatibility guarantees, security policies, etc. are actually critical components would probably not ever make the decision to take on that engineering burden themselves unless it were a business differentiator, which it almost never is.

> Not to mention that the interesting parts of your app should be the domain logic and workarounds and solutions used in it for business issues and historical layers of bussiness logic choices.

In my experience this has been a point in favor of OTS frameworks--the code you don't care about is handled by the framework, and you bring the business logic. But also, reading through this, I guess I don't understand your comment. Isn't the business logic in the code? How can a person take it with them?
So wings _do_ work, then?
By that logic, every algorithm is O(1). You first limit it to a single input, then you “correctly define” the output for that input using some fixed length string, and you’re golden.
Still a parenting issue! Just a bit late.
Wave-induced power generation system (1min video)
Hay does have a lot of secondhand bookshops and their existence has elevated a small backwater of a town into a successful tourist destination. However, in recent years a lot of bookshops have closed - becoming antique/curio shops instead (source Wikipedia). I suspect that many of the tourists to "The Town of Books" don't buy enough books to sustain the local economy.
>> [contains] soy protein concentrate, sunflower oil, beetroot powder and yeast extract.

With these kind of ingredients no health consious carnivore will ever want to touch this.

Meanwhile in the real world:

>> However, the plant-based meat industry is having a tough time. Shares of Beyond Meat (BYND) are down more than 75% this year, near an all-time low.

Basicaly these are ultraprocessed food companies shilling under the guise of "we are climate change savers!!!!111".
RCS is not SMS. It’s just some unrelated technology making a claim to succession because Google said so.
setting showrooms aside as they feel useless,

you start off in the impulse buy areas, and leave through the bleak self-service areas. This doesn't jibe with the "ikea intentionally makes you tired to make you impulse buy" narrative
You misunderstood, I wasn't advocating for communism but our current system is definitely flawed and unsustainable long term.

So you're telling me that we should allow people to own pieces of the planet earth forever? Sorry, but how is that sustainable? How is it fair the someone gets to own large swaths of the planet and use it as leverage to buy even more of it, just because his great granddad came to an empty country and got land basically for free which now make his grandchildren millionaire landlords even though they didn't contribute to society in any way to earn what they have and if they were to buy their property at current market rate they wouldn't be able to afford even 10% of it.

This may have been the foundation of societies, thousands or hundreds of years ago, but what was the population of the earth back then and what is it now? This system is not sustainable, and just like laws, it should be updated to account for current conditions.

Our current system is flawed as it just comes around full circle to creating a society of a few landlords owning most of the property and assets and the peasantry which can't afford to own anything. And looking back on history we know how that usually ends. We need a new system that resets the monopoly board fairly instead of waiting for social uprisings to boil due to increased wealth inequality.
The xonsh shell can use sqlite for history. Really useful, also contains runtime statistics, for instance. I used xonsh for a few weeks. It is absolutely an awesome shell, but I didn’t find the switch worth the effort personally.
That would deserve its own submission
Free / open source code can be _forked_ by anyone, but in doing so one often takes on a maintenance burden bigger than one's current codebase.

To have a fix accepted on an OSS project means fixing it not just for your use case but also for every other user of the project, on every target platform, while aligning with the goals of that project. If you can get anyone to look at the PR in the first place. Assuming you've used the framework to save time, you probably don't have time to go through all that and your deadline will not wait a month or six for your code to make it into a release. Depending on your employer you may well need internal permission and legal sign-off to contribute to an OSS project in company time which is yet another hoop to jump through; though that goes for forking too.
>> The problem is the onlookers don’t know why you’ve fired someone; they’re free to assume whatever they want.

> You can and should address this.

Except that you can't address this. You can say whatever you want, but it won't result in onlookers knowing why you did what you did. You were probably lying.
Maybe GNU Social?:
https://en.wikipedia.org/wiki/GNU_social
There's a limit to how much you can shrink the battery. Max current goes down proportionately as well. You could certainly stress the cells beyond their operational envelope a bit to set a record, but even then there's going to be a hard ceiling, and it's presumably an I^2 situation rather than linear. The optimal battery size for a single acceleration is probably smaller than 100% of the production battery, but it's probably not much smaller.
I meant, in justification of the amount in the sanction (consistently with the concern of the parent poster).
I think another issue with compressing partial content is that those compressed responses cannot be cached efficiently - it would have to be compressed on-the-fly for every range requested. And while compression is not as computationally expensive as it used to be, it does still add overhead that could be more than the bandwidth overhead of uncompressed data.

There should be a workaround for this using a custom pre-compression scheme, instead of relying on HTTP for the compression. Blocks within the file will have to be compressed separately, and you'll need some kind of index mapping uncompressed block offsets to compressed block offsets.

Unfortunately there doesn't seem to be a common of-the-shelf compression format that does this, and it means that you can't just use a standard SQLite file anymore. But it's definitely possible.
I agree, although I'm really curious about what the post-Zoomer generation does with VR.

Our media and how we interact with it has only ever trended in one direction: higher bandwidth.

The generation that grew up with oral tradition loved the written word.

The generation that grew up with the written word loved the printing press.

The generation that grew up with the printing press loved photos.

The generation that grew up with photos, loved videos.

What will the generation that grew up with video love? It certainly seems limiting if they settle for merely a higher resolution, FPS, or better sound quality.
I love these technical topics because I can open up popcorn bag and read how people with statistical significance of 1 person experience throw their opinions and claim they have it all figured out.

In my 14-15 years of experience in software industry I learned that having framework helps mostly with that - having bunch of "know it alls" rounded up to use the same approach instead of having "I know better discussions".

Where frameworks shine is specifically lowering amount of discussions on technical details that has no relevance to the business but has all kind of opinions from devs.

Someone in the thread claims - if he is hired he has to learn framework - well I am hiring people with knowledge on framework we use, he might not have been looking for a job lately. I have not seen we hire c# or c or java dev - there is always framework in requirements. Just see how frontend devs ads look "react dev to hire"/"angular dev to hire" no one hires "someone who knows html and css", yes it is requirement to know these but you also have to know at least one framework.
Show HN: We Built a Documentation Recommendation System Using Graph Database
> rapidly rising commercial rents in many big cities.

I thought the problem was people were not coming back to the office? Why is commercial rent rising? (Do you mean retail rent?)
Hi! I'm one of the authors of the documentation recommendation system we built during the summer internship. We wanted to create an engine that would help users to navigate better through a certain documentation. As our stack we have used the following:

1. The MAGE graph library[1] - for already implemented graph algorithms

2. GQLAlchemy[2] - a Python driver and Object Graph Mapper (OGM)

3. Docker[3] - for building and running the application in a container

4. Memgraph Lab[4] for graph visualizations.

In the blog post, we described the approach we took to build our app. You can check out the code at our GitHub repo [5]. If you have any questions, feel free to ask me :)

[1] https://memgraph.com/docs/mage/installation

[2] https://memgraph.com/docs/gqlalchemy/installation

[3] https://memgraph.com/docs/memgraph/reference-guide/deploymen...

[4] https://memgraph.com/lab

[5] https://github.com/memgraph/docs-recommendation-system
The traditional destination for spectacular Uk political falls (EU Commissioner) has been blocked.
Plz share. If a hole exists, interested party will know about it, sooner or later (or already). So, IMHO it's better if just everyone knows. This is only my opinion.
Might need some Apple Silicon testing, I could toss and egg on my M1 MBP and it'll be done by the time I scroll to the bottom of the document.
both of the links says, "job not available".