skysight-inc/HackerNews huggingface dataset:
Web Developer Industry – What happened last month?
>>the needs of the tenants trump the needs of the landlords

> Which tenant? The one that is currently in the building, or the one that could move in and pay rent?

The one currently in the building. This is quite clear cut, the two tenants are not equivalent.

Rationale:

The one that could move in and pay straight away almost certainly has a place to live already. It's possible they are currently homeless and yet able to start paying immediately and convince you it's sustainable, but it's very unlikely.

The one being asked to leave is likely to end up homeless, in a pandemic. Unless your place is significantly above market rates and there's a realistic cheaper place available to them. Even if there's a cheaper place they could move to, with all the checks in place, most potential new landlords will reject a tenant who just got kicked out of somewhere for non-payment of rent. There may also be high competition for a small number of "last resort" places to live which accept people in this situation. And moving when you have no money is also very difficult, sometimes impossible and they will lose their possessions too.

So if the value being prioritised here is to minimise avoidable homelessness, then priority should be given to the person who would be made homeless, not the person who wouldn't.
Synology OS is a modified Linux and it uses mdraid for RAID. There is no hardware RAID, and very little closedsource bullshit.

This is how you'd mount a synology array in a Linux server: https://www.synology.com/en-us/knowledgebase/DSM/tutorial/St... - it's basically two terminal commands after all the preparation stuff.

I believe QNAP uses mdraid as well but I haven't had any experience with those.
Python Industry – What happened last month?
All I can say is "good luck with that".
Ad Tech Could Be the Next Internet Bubble
The wait time will be the same but the amount of wasted CPU won't.

It's not a lot but it adds up. If it's only on your servers then whatever, but if the code goes to clients then please wait on an event.
> since you can't predict the future

That's one of those statements that makes sense, but is often not true. Very rarely does a client comes to me with a feature request that does require a pretty significant design change, but most of the time they're changes that were foreseen.

Using this current article as an example, I love the way that they're storing the intervals to guarantee that they can't overlap. That's awesome! What I would likely end up doing, though, is use that as the underlying representation but still return individual interval objects through the query API with a start and end date on each interval. That way, if the "only one at a time" rule changes, the changes required are localized.
that's not a valid argument. How do you identify "the lot"?
You gradually replace one disk at a time, resilver then repeat. ZFS automates most or all the work mentioned in this article and it comes with built-in bitrot detection.

Btw I have run a NAS similar to this machine for 6 years now using FreeNAS. It’s awesome.
It's possible, if a little annoying. In your account settings, Amazon offers the ability to download an e-book to transfer via USB. This gets you a version that you can import into Calibre and process with DeDRM.
I would equally argue there is nothing wrong with the local work history branches being remotely available. If I have multiple branches for one ticket nobody ever seems to care, they just care about which branch is in the PR. Besides, if you have a reasonable web UI for git, it shows it all merged together as one big changeset.
Right. The problem is that are two use cases for commits:

- a historical, fine grained log of changes

- and a log of merged features.

There's value in keeping both of these data sets. But the commit log as it stands can't easily serve both masters.

Once you can see the problem for what it is, the solution is simple. Instead of conflating these two use cases into the concept of a 'commit', we need separate tooling for each of these use cases. The commit log should probably house the historical record. And then we need a way to mark a set of commits as belonging to a particular feature's development. That could be achieved either by adding special support in git or via convention using commit messages.

Either way, I want to be able to see the commits in my repository grouped by the feature that they belong to. And I want that data set browsable on github, referenced against the corresponding github issues when thats appropriate.
what about the tax regime?
I've read the opposite, or at least that they are very close, from an unbiased (as far as I can tell) source. Couple that with all the reports that investors in e.g. Germany are extremely conservative and it seems social mobility would be lower.
Hey HN!

My name is Dan Zaitsev, and I'm bootstrapping with my team a global web-community for Augmented and Mixed Reality creators.

We would like to share with you our new feature and get some feedback if acceptable. Also, we have some pending questions where we need your advice.

Recently, we released an asset store / marketplace where creators and companies can list for sale their AR, MR, ML templates, models, source code and tutorials. Currently, this feature is in early beta, and now we present assets related to Spark AR and Lens Studio; more frameworks are coming soon...

Why did we release it?

We found out that some creators use PayPal, Gumroad and Etsy to sell and monetize their assets. However, creators from the CIS region, Georgia, Ukraine, Asia and some other countries are limited in payouts from these services. We partnered with one PG to organize direct payouts through SWIFT and SEPA.

Here some common questions where we need your feedback and advice:

1. What are your thoughts regarding our new asset store / marketplace module? Can we compete with Gumroad, Etsy and other top platforms where currently creators sell their assets?

2. Do you have any ideas on how we can protect our creators' IP (intellectual properties)? Meaning, when some scammer buys assets on our website and then goes to another website and sells them there? This is currently the most common problem of creators who try to sell their templates, patches, etc.

3. The last question is about positioning. Currently, our community and marketplace about Augmented and Mixed Reality domains. But we also have lots of creators who specialize in Machine learning, Training models, Open CV, etc. Should we drop the message Augmented Reality or keep building a niche community?

Please let me know what you think. Thanks!

Best,
Dan
“Children Born after Autism Epidemic are Mentally and Physically f–ked up”
You don’t need to upgrade at once. You can upgrade gradually with the right config.
One can branch and then merge features, and get easily revertible commits and a full history at the same time.

Of course, there are caveats for reverting a merge - finding the right parent adds another failure-prone step, and your team can get in all sorts of trouble if they try to work with the branch without reverting the revert.
I think a better way to phrase it is that reinventing the wheel has very little business value.

But IMO you can learn a lot reinventing things badly and correct software has little business value anyway.
This is not the issue at hand. People are looking at this and trying to tie it to all kinds of things, like environmental policy, or the right to repair. All of those are valid issues that have specific policy goals behind them but his is much more straightforward. Apple contracted a recycler to destroy the devices, and those devices made it out to the market, breaking contractual obligations. That's it. For some reason, you want to nitpick specific reasons I listed why a company may want to destroy devices, but that's not the point. You and I don't know the reasons, don't know the space, don't know the business, don't know what we don't know, we're just two guys speculating on things we don't have experience in.

I am confident in arguing, however, that in whatever regulatory regime we are in, there will be times and good reasons for destroying or landfilling devices.

I'm happy you have a secondhand Thinkpad. And I'm happy you got an endorphin rush for telling people on the internet that you have a secondhand Thinkpad - but you are going to landfill that device. Also, I hate Apple devices. I think OSX is overrated, and both OSX and iOS have terrible ergonomics. And yes, Mac computers and laptops are overpriced and their quality varies from year to year.
Well the only owner is the copyright holder
It's not that much more complex: if you do

SELECT event FROM events WHERE startDate < "2021"

then all but one of the results (the one with the greatest `startDate`) will also have an implicit end-date prior to 2021.
rebase will give you linear history, merge doesn't provide you that
Bisect doesn't have a problem with intermediate broken states, actually. It's why git bisect skip exists. It may not be able to pinpoint an exact commit though.
That's not what would happen though, by default the resulting commit message contains the messages from all those squashed into it.
There is definitely some kind of miscommunication here. I know the area well enough (Sverige lite bättre än ditt land men iaf...) that your comments puzzle me.

I know that you know that poverty in your country, compared to the US, is a non-issue.

I know that you know that citizens in your country don't have basic educational deficits that many Americans have.

I know that you know that your country is very capable of competing in the world market.

As a reminder of the scope of the differences, see: https://youtu.be/YEywCppqeZo or https://youtu.be/JHDkALRz5Rk

So, I too am confused.
>The defense system is called MOSE, the Italian for Moses, a name derived from the more functional Modulo Sperimentale Elettromeccanico, meaning Electromagnetic Experimental Module.

Elettromeccanico translates of course to electromechanic, and there is nothing actually "magnetic" in the project.

https://en.wikipedia.org/wiki/Acqua_alta#Countermeasures

As a side note the MOSE is pronounced "plain", while the Italian for Moses is Mosè (accented on the last e).
What do you use your "cleaner history" for? I seldom go back and look at historical commits unless I'm debugging, in which case I'd prefer to know what actually happened at the time with as much information preserved as possible.
But, this was done by third-year students in an educational context. It is just a way of learning by doing instead of by only studying books, and even bright students have to learn the basics first.
Can anyone with more of a background in central banking describe what this means in more concrete terms (or explain that this is fluff). The best I can find for what this means is in the PDF

"In this report, the term digital euro denotes a liability of the Eurosystem recorded in digital form as a complement to cash and central bank deposits. The analysis focuses on the design of a digital euro for use in retail transactions available to the general public – that is, including citizens and non-bank firms – rather than only being available to traditional participants (typically banks) in the large-value payment system managed by the central bank."

Is this not how the system already works? Presumably there is not a 1 <> 1 mapping of owned Euros to bank note/coins?

The report talks a lot about unbanked people, innovation in payments and so on, but I don't really see how those things relate.
Does it work for people in Europe?
Everyone who works on Linux must rebase and squash commits so that every commit builds and passes tests, and does a single thing. More about how Linux uses git:

https://www.mail-archive.com/dri-devel@lists.sourceforge.net...

https://www.linux.com/news/why-linuxs-biggest-ever-kernel-re...
536 Regal theaters in U.S. closing October 8; 40k U.S. employees impacted
This is already the rule on HN, the submitter must have forgotten (it happens!). A mod will likely change the title.
Things You Should Have to Succeed in Online Affiliate Marketing
You don't have to squash into ONE commit just because you squash.

If I make 10 commits I can squash it into two logical commits (e.g. refactor, add feature) then I merge the branch with those two.

If the branch is small and has 3 commits that are one logical change, then I might as well squash to main instead of merging.

Commit history is readable regardless (I'd never use anything but --first-parent ever).
Adhering to OpenApi 3.0 spec https://swagger.io/docs/specification/about/ you will be able to take advantage of plenty of tools available to you, regardless of the programming language/framework chosen to build your software.

It's not always possible or desirable to have back-end models and controllers auto-generated from OpenApi spec, but still I totally recommend to make an extra effort to keep documentation and API in sync since day 1 as API is evolving.

Document an API it's definitely not an easy task, but it pays off - specially if you plan to have third-party developers consuming your API in the future beyond your own engineering team.

Some important points I try to be disciplined about, based on my own experience building APIs in C#, Delphi, Go, Java, Node.js, PHP, Python and Ruby:

1) Document your API from day 1

2) Update your API docs every time you commit a new change to your models/controllers/endpoints

3) Test your API docs against your actual implementation. Dredd is a great tool for that: https://github.com/apiaryio/dredd

4) Build an API client from day one (web app, command line app, desktop app, whatever), and use it for testing the consumption of your API endpoints, and update it every time your API changes

* Benefits:
you're gonna have a perception of the developer experience that your API users are going to have when consuming it, and very likely that will bring you some insights on opportunities to make things simpler or better documented (header params, query params, request payloads, endpoints signature, response status codes, ...)
Why is Anbox only distributed as a snap?

Anbox is currently only distributed as a snap as snaps makes the life for us developers pretty easy. They allow us fast and easy packaging, easy distribution to our users, as well as regular and fast updates. Flatpak would be another alternative but we didn't investigate this yet, nor are we planing to do so in the near future. However, we're happy to accept contributions from the community around Anbox to provide necessary changes to distribute Anbox as a flatpak package too.

One thing which Anbox currently doesn't do is using proper confinement for snaps. Right now it is only usable when installed in the so-called devmode of snaps which disables any confinement. This is something we will work on over the coming months with upstream to allow our snap to be fully confined.

Despite snap confinement being disabled, the Android system still stays separate through the use of Linux namespaces from the host system.
It is not related to squashing or not. One of the main rule when using git (or any other VCS I guess) is that each commit should be atomic.

IMO squashing commits is something that you should do locally, not remotely. For example I'm currently debugging a fairly large C application on an embedded system. Each bug has it's own branch. When debugging / testing / trying to fix it I tend to do a lot of commits. When the bug is fixed I do an interactive rebase to pick / drop / squash commits in order to have only a clean one at the end (and then push it).
A rolling 3 year contract renewed each year would be a huge improvement compared to the constant nagging feeling of being throwed out anytime the contracts end.

I worked as a research engineer for 2 years at an uni but since I was not full time employee for real I left. They would have needed way more full time engineers than zero. You can't run serious labs with grad students or short term engineers. The churn is way to big when you work on a per project basis.

The advantage state officials usually have is a safe paycheck with worse pay but unis offer the same numbers on it without the safety ...
Free YouTube to MP3 Converter 4.3.19.701 Crack Download
The 21st Century Renaissance – The Education Century
Commit history serves two largely separate purposes:

1) To provide a code-level record of what has changed in individual files and why.

2) To provide a high-level record of what features were introduced and what bugs were fixed over a period of time.

Often people will forget about one of them when arguing for a particular approach.

Squashing can make 2 easier but annihilates 1. Rebasing gives you 1 but makes 2 difficult, or requires that you track high level changes in an external system. In theory, approaches using merge commits can give you both but they are often difficult to apply in practice.
I don't think we should have to sign Eula, if i can buy a book without one, why cant I buy a game in the same manner? You are, equally, not allowed to duplicate and resell either of those.
The context of the point is that Climate change's max increase is only another 0.5celcius and at worst the currently too cold places will become warm enough to live comfortably.
Yes. But also: Granularity undermines the effectiveness of bisecting when your commits aren't ACID.

These conversations are so often tedious and repetitive largely because engineers seem incapable or unwilling to apply systems thinking to development practices.
I wasn't a fan. It was a bunch of disjointed essays rather than a real history. The later parts really deviated from the promise.
Even in people with Parkinson's gene, coffee may be protective
Surprised to see no mention of Japan in the comments. As any visitor can attest, the country has way more vending machines than anywhere else I know of, and in way more categories. Soft drinks, tea (hot and cold), coffee, beer, hard liquor, tobacco, snacks, ice cream, rice, toiletries, even the semi-apocryphal used panties.

The article below outlines some reasons why, but it seems to boil down to high cost of labor & real estate, high population density and heavy public transport usage. In suburban shopping arcades (shotengai), which by and large are dying a slow death, it's not uncommon to see closed stores that have literally been replaced by a vending machine or two (often owned by the store owner) retailing the same products, particularly for liquor and tobacco.

https://www.businessinsider.com/why-so-many-vending-machines...

Not that Japan has the monopoly on weird vending machines:

https://www.norwegiansalmon.com.sg/
you can use deepl.com to translate it to different languages instantly :)
By the ticket/issue number?
RNA viruses exist. They exploit the highly "artificial" conditions inside living cells, where these unstable components are constantly being constructed and undesirable chemicals excluded.

A primordial soup, without the precision enzymes and constant energy expenditure of this synthetic machinery, will be a grab bag of random glop. In Miller-Urey experiments the concentrations of any particular chemical decline exponentially with the number of atoms in that chemical. I believe ribose has never been seen in any such experiment (and certainly not in any but extremely low concentration), never mind the triphosphorylated nucleotides that provide the energy to drive RNA synthesis.
You very rarely want to rollback a major feature. I’ve never seen it done except right after a deployment, in which case you can revert the merge commit instead. Bisect to find a breaking change is a very common operation. Squashing is bad if you expect to work on your project long term or if others may have the same commits as you from working on the same feature branch.
The standard is followed so infrequently that quoting it is basically an exercise in needless pedantic detail mongering. It's just not very relevant, probably because the rules to check valid email are so ridiculously complex (how long was that regex, 200+ characters?).
Pronouncing Qt as Cute is like pronouncing gif as jif. Maybe someone 'officially' says it's correct but basically no one does it and if they do, everything secretly judges them.
+1 for Gatling. I agree with the reporting part. Although the basic version is good enough for the 80% use case
You also get loss of smell with hayfever.
Honda has committed big time to the Indy series where they are one of two providers of crate motors.

It all comes down to this: the F1 racing "product" sucks. Indy racing is night and day more entertaining. That's also why Liberty Media (who owns F1) just invested big time in an Indy team.

I do not think it's more complicated than that.
The fix is very easy: forbid fast-forward merges, and then you can always revert the merge commit of particular feature branch.

As for cleanliness of history, everything should be as simple as possible, but not simpler. Squashing and rebasing is destroying history, which often could be valuable, as OP shows.
Well, except for the JVM of course.
A hypothesis linking diet and Alzheimer's disease
Yep, but many tools (most notoriously git bisect, famous from the article) doesn't understand "--first-parent" which is ridiculous.
The only way to have a clean history that all tools accept is clean, is basically to outlaw merges.
When 90% of the other computers on the planet do it differently?

I’m pretty sure that I can make some assumptions about what is going to be obvious to most based on that alone.
Which is a shame, because O'Reilly stopped selling ebooks more than three years ago: https://www.oreilly.com/content/the-mission-of-spreading-the...
> When the sport was awash with tobacco money about 15 years ago, the big teams all had an entire testing team

So, we just need companies with a lot of money that are interested in technical advances and advertising and don’t care about RoI like banks might? What about Google, Apple, Microsoft, Oracle, Salesforce, ... any takers?
And I believe DEC gave Linux a 1 or 2 alpha systems to work on the port
> If I rollout a rewrite of an endpoint and run into a weird issue in the QA environment, I'm a simple git revert away from fixing the issue

I'm firmly of the belief that any benefits that squashing brings would be better achieved with better tooling, rather than by re-writing history and throwing away potential debugging information. In this case, what you need is for git to make it easier to revert 25 commits in one go
If there's any spare land left where you're allowed to build and live, sure.

In some countries there is. In some there isn't. Where I live, no chance, people who have found unoccupied patches and built on them tend to eventually have their property destroyed by government.

So maybe you're thinking, move countries.

Nope. A lot of people in the world are prevented from moving to countries they'd like to move to. Heck, sometimes married couples are prevented from being together. It's a pretty restrictive world.
Obrigado. Just for information, forro has some popularity in germany: https://www.youtube.com/watch?v=c33sqgUUJKg
Worth mentioning that, while the `git bisect` algorithm is pretty easy to run by hand if you have a linear history, `bisect` also handles very complex branching and merging histories as well. Very clever and worth using!
Bisect does turn into my colleagues feature branch with 20 broken commits and unrelated content though, when I just want to bisect the main branch. That's infuriating and imho makes bisect almost useless. That there is no git bisect --first-parent is one of the greates mysteries of git.
Just use the language of the business/domain to write your model/API. No need to reinvent names and rules that already exist. Do whatever you want with the underlying implementation, your DB, etc.