skysight-inc/HackerNews huggingface dataset:
> Why not just add a "use new_defaults;" pragma or something that just turns on this handful of new options?

Umm. Yes exactly.
The thing is that it will instead be spelled as:

use v7;

There is already plenty of precedent for doing exactly that.

use v5.10;
## enables the use of `say` `state` etc
# use feature qw(say state);

use v5.12;
## does the same as above but also
## - makes `use strict` mode the default
## - enables 'unicode_strings' feature
# use strict;
# use feature qw(… unicode_strings);

use v5.16;
## all of the above, plus
# use feature qw(… fc current_sub unicode_eval evalbytes);

use v5.28;
## all of the above, plus
# use feature qw(… bitwise);

One question is what quantity and quality of changes are necessary for jumping from `v5.xxx.yyy` to `v7`.

There is also a question of what happens if you don't have a `use v_;` or equivalent statement.

(This is not an exhaustive list of questions.)

---

Personally I would think that `v7` should make the currently experimental signatures the default. It should also make the new Cor class experiment/prototype available with the `class` keyword. (Perhaps even a `method` keyword, but that is not strictly needed.)

Since both of those are currently being developed/designed, I think that `v7` should wait until then.

---

Other things that `v7` _might_ enable/change is things like the following.
(Slightly edited from: https://stackoverflow.com/a/6163129/1337 ) I am not necessarily suggesting any of these, they are just possibilities.

use utf8;
use strict;
use autodie;
use warnings;
use warnings qw< FATAL utf8 >;
use open qw< :std :utf8 >;
use charnames qw< :full >;

use feature qw< say state switch unicode_strings
unicode_eval evalbytes current_sub fc
postderef_qq bitwise >;
no feature qw< indirect >;
use IO::Handle;

use File::Basename qw< basename >;
use Carp qw< carp croak confess cluck >;
use Encode qw< encode decode >;
use Unicode::Normalize qw< NFD NFC >;

END { close STDOUT }

if (grep /\P{ASCII}/ => @ARGV) {
@ARGV = map { decode("UTF-8", $_) } @ARGV;
}

$0 = basename($0); # shorter messages
$| = 1;

binmode(DATA, ":utf8");

# give a full stack dump on any untrapped exceptions
local $SIG{__DIE__} = sub {
confess "Uncaught exception: @_" unless $^S;
};

# now promote run-time warnings into stack-dumped
# exceptions *unless* we're in an try block, in
# which case just cluck the stack dump instead
local $SIG{__WARN__} = sub {
if ($^S) { cluck "Trapped warning: @_" }
else { confess "Deadly warning: @_" }
};

It might even start using object based exceptions by default.

Again, one of the questions is what quantity and quality of changes are necessary for jumping from `v5.xxx.yyy` to `v7`.

(My only real opinion is that I think that signatures and Cor-like objects should be included. So it should wait until their designs are fully hammered out. The rest can be done in stages with `use v5.xxx.0;` until then.)
Philips SHP9500 headphones, TIN HiFi T2 Pro IEMs, AudioQuest DragonFly Black DAC.
Adding those two things up, it sounds like it says

A person that is in the business of offering an online platform to connect third parties to an online marketplace, exchange, or search engine may not provide online hosting services or back-end online services to any other entity that is not owned by the covered person.

I don't know how you offer an online platform without providing back-end online services.
It's probably a lop sided u-shape. Most people lacking in self-awareness are either really smart or true outcasts, with 'high conscientious + good communicators' occupying most middle management ... but it does take a kind of hubris sometimes to overlook one's faults, even worse, to completely ignore them otherwise. Without being controversial I see hints of this in Jobs, Ellison, Trump, Musk, Page, Zuck etc. (again I'm not condemning here, if any one of us put our thoughts online consistently there'd be a few we would seriously regret).
Would an extension like citus or timescaledb or opengis be considered a combined work for AGPL purposes?
Also one account where I can see all the comments I've left on the various sites with their replies. And if I feel like it, I can easily remove old comments - even after my nickname and/or email changed, I've deleted all my cookies and/or got a whole new system. I just need to be able to log into my Disqus account. And the site I'm commenting on doesn't know my email address.
Tell the kids that it's "educational", and they'll ensure they don't hear a word of it.
The GPL and AGPL are clear that bundling does not constitute a derivative work, and does not require you to license the bundled works under the GPL/APL.

> Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
https://www.gnu.org/licenses/agpl-3.0.en.html#section5

https://www.gnu.org/licenses/gpl-faq.html#MereAggregation

If you write a custom plugin for Grafana, then that plugin will likely need to be distributed under the AGPL (depending on Grafana's plugin architecture), but not your entire app.

I would be completely confident in bundling in this manner. The AGPL3 and GPL3 have identical wording on this matter, and it has been a well understood aspect of the GPL for decades.
Yes, corporate press releases are an exception to the usual HN title rule. I'll change it back.

https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...
You have 64 GB swappable memory, can cheaply upgrade it up to 128 GB without voiding the warranty. You have 10Gbe Ethernet. You have bigger screen. Why sell now?
Ah, that would explain why "covered person" and "covered company" are used seemingly interchangeably without "covered company" ever being defined.
It’s ok. Google banned the terms “first class” and “second class”. Problem solved.
In the UK, there's an aspirational kitchen stove brand - AGA, which are intended to run 24/7.

I understand it takes a fair bit of experimentation to learn how to cook on one. :)

https://www.agaliving.com/products/aga-cast-iron-cookers
It's not really that surprising. At some point the established players ossify and are unable to innovate when the playing field changes.

A new thing comes along without this problem and dominates the new playing field. For Teamspeak and Ventrilo the field changed in that it became possible to host the voice servers themselves, rather than the 'customers' hosting.
Tested this. Unbuckling turns it off, but lifting off seat doesn't trigger anything. Obviously didn't try actually not being in seat completely. More here: https://twitter.com/Singularitarian/status/13841868748104417...
> If you do like the GPL this merely fixes an important corner case.

Disagree. As the article states, it's importantly different from the GPL, even under the FSF's own philosophy. As others have already pointed out, it could be said to infringe on Freedom Zero, The freedom to run the program as you wish, for any purpose. [0]

At the risk of just writing a far inferior rehash of the article: under the GPL, you can take code, modify it (Freedom 1), and run that code on your machine under whatever terms you want, e.g. as an Internet-enabled service. You are not obligated to publish the resulting source code, provided you also refrain from publishing the binaries corresponding to the modified source. With the AGPL, that's no longer the case.

One could argue it's just a matter of degree, as the GPL imposes rules on linking against non-GPL code, but I think the difference is still an important one.

Following copyleft, the FSF understanding of being free to do something typically doesn't preclude free but with an obligation to release your source under a Free Software licence. They do seem to have a limit though. The FSF consider the Watcom 1.0 licence to be non-Free because of its far-reaching source-publication requirements, which can apply even to private use. [1] The AGPL does something similar, except it only applies when your deployment is publicly accessible. (This is, of course, the whole point.)

Quite apart from all that, this isn't the first time I've read of technical legal issues with the way the licence is written, far exceeding those of the GPLv3.

[0] https://www.gnu.org/philosophy/free-sw.en.html

[1] https://directory.fsf.org/wiki/License:Watcom-1.0
Plenty of us. While Node.js might not be talked about as much as Go or Rust is, it's battletested in my opinion and a breeze to work with. I'm currently using Node for a large-scale content platform that is comprised of an ingestion engine, a parser, a queue and scraper. 4 Node servers powering 40k+ sites, sitting behind a load balancer, NGINX and PostgreSQL. It's not using anything overly fancy, but is stable and easy to fix if anything goes wrong.
I prefer to opt for the more fun option, but it's generally an immaterial change.
This sounds wrong. Since Matrix is federated, you can still be echelon, just not @echelon:theserveryoutried.com.

Furthermore, this is just the MXID, the Matrix ID. This is usually de-emphasized in the UI and only used to disambiguate and add users (as you say).

What is usually displayed to users are display names and these are allowed to have collisions, in which case they get disambiguated via MXIDs.
Radical social justice is a form of ultimate conspiracism. It immediately attributes abject malice to every phenomenon it observes. According to this worldview, Richard Dawkins can have only one possible motivation when writing about transgenderism. The acclaimed author, thinker, and a lifelong apologist of scientific truth only makes his claims because he wants to demean a disadvantaged group. This man only pretended to be an iconic intellectual for many decades, only to show his true racist nature today, and there can be no other interpretation.
Yes, it’s a broad industry issue that companies like Facebook will ask us for our phone numbers and promise they will only be used for authentication [1], and then leak them by publishing them on the Internet and letting third parties scrape them... I’m not sure it’s a problem we should normalize though.

[1] https://nakedsecurity.sophos.com/2019/03/05/facebook-critici...
It's less questionable than incorporating permissively-licensed code into a proprietary product.
On the Impact of Programming Languages on Code Quality, a Reproduction Study [pdf]
YouTube demonetises James Charles over sexual misconduct allegations
Your plan would put Facebook, which gets data from people, in a better position, since they collect data on people with those people's permission, in exchange for services. They just have to assign a dollar value to their services and they would have fulfilled your requirements. Where yeah, it would nice if credit companies had to get permission too.

And nearly every website already warns me they're going to collect data. With you're step, the next thing is signing away that rent.

Or, if your plan involved rent that can't signed away, well, no one would host anyone for anything since they wouldn't want to pay that.
> Why are any of us going to do any better and why does a few hours of downtime ultimately matter?

The answer is surprisingly simple.

Most outages are the unintended result of someone doing something. When you are doing things yourself, you schedule the “doing something” for times when an outage would matter least.

If you are the kind of place where there is no such time, you mitigate. Backup systems, designing for resiliency, hiring someone else, etc.
There's similar set of tools by notaz[1] that were used to static recompile starcraft, diablo, diablo 2, and jazz jackrabbit games to ARM Linux. You can read more about the recompilation here[2].

1: https://github.com/notaz/ia32rtools
2: https://www.giantpockets.com/starcraft-pandora-port-came/
They are the winners in a corrupt game, and it's easier to hate the player than the game.
IMO, Tk is by far the best for targeting multiplatform desktop. Qt is a close second and Gtk is "sticks out like a sore thumb, but works"

I don't think Tk runs on iOS, which is why Tk is usually disqualified in "multiplatform" recommendations

MAUI and Xamarin.Forms both have "okay" linux support last time I checked.
Many people felt the same way about tweeting. I doubt it makes enough of a difference to matter one way or the other.
This would be super nice to have when developing mobile apps. I’ve used sqllite when developing with react-native, but can see myself using a mongita type solution.
EPA approves first release of genetically modified mosquitoes in Florida Keys
For example, Amazon could not simultaneously operate Amazon.com (the e-commerce website) and AWS (the cloud provider). They'd need to choose one or the other.
The information that was scraped here, though, are phone numbers that Facebook requires you to add to your account and that they promised would not be used for anything other than authentication purposes. Most of these numbers should not have been publicly available in the first place.
Is that true? Firewood comes from downed/dead trees (unless a tree is felled for some other reason). I thought the same amount of carbon was released whether a dead tree rotted on the ground or was burned for heating.
desolder the speaker or piezo.
> I’m guessing because the vast majority of the market with a 4K Apple TV is not watching in stereo, but in surround with something like Dolby Atmos

I bet a chunk of money it is the exact opposite. I bet for the majority of the market the fanciest thing they have is a soundbar and maybe a subwoofer.

I honestly think the "home theater" market is pretty niche. It requires living conditions that most people simply don't have. You gotta have the right room shape for starters. Virtually every house I visit doesn't have a room that is easy to set surround sound up in.

I mean for Atmos you specifically need speakers placed above the listener. Not to mention a bunch of other speakers everywhere.

I dunno... almost nobody is living an a place amenable to such things. And even if they are, they need to get consent from their significant other to pull it off.

So yeah. I bet maybe 5% of the market has Atmos or any kind of surround sound. 15% tops.
How does the manufacturer have the owner's email after something like a private resale? Would they just send the consent request to the original purchaser?
What happens when the emails fail (like spam folder)?
I remeber a thread here on HN on a number of projects where they dumped email link sending as a login method for various reasons and complications. Have you face any challenges as well? If not what's your secret sauce? A better email provider? Would love to know.
It's amazing in an extremely depressing way, but it's still impressive that they get away with it (assumedly, given the sales of the other devices). The benefits of a walled garden, I suppose.
Firecracker is a fork of Googles crossvm, not an original Amazon project.

I bet it wouldn't be open source otherwise.

Also, it's a more convenient and secure shell around kvm. It's valuable, but bit that meaningful.
Well that won't work... former President Barack Obama received the Nobel Peace prize but he went on to involve the United States in additional foreign wars and went ham with drone strikes.
Smoke on the water, a fire in the sky: iPhone XR catches fire on plane
Agreed; one is a subset of the other. I tried to say something like "open-source in general, and its more strictly licensed copyleft subset,..".
Well, GPL is about freedom for the users, not necessarily for the developers.
Ask HN: Did your employer's IPO help your career?
If you have worked at a company at the time it IPO'd, did that have any effect on your personal career?

I work at a company that will likely IPO in 2022.
After working there several years I've been feeling restless, thinking about moving on. However I'm wondering if it makes sense to hang around until the IPO.

I don't mean in a direct financial sense - more whether your employer's IPO led to interesting opportunities, gave you credibility, was really fun, or other positive side-effects.
Being a native English speaker from another country I don't possess this association at all, and have to dig quite deep to remember that Americans do.

I do get tootsuite => toute de suite i.e. a sense of immediacy, the present moment, with greater impact for being a bilingual pun. Along with that, the onomatopoeic elephant.

Cynical take: notwithstanding the denial in the PR, that original author knew the scatological allusion, and that it has parochial scope, i.e. they actively intended to annoy Americans, and in particular those with a prim streak.
You can't invent your own definition of end-to-end encryption.

There is a material difference between a service which end-to-end encrypts your files – even if it sends you the code to do so – and one which does not.

Services like Dropbox or WeTransfer receive plaintext copies of your files. Firefox Send did not. And Wormhole, using the same design, does not either.
Yes, but this time:

- They're going to support MVVM and MVU (MVU is similar to JSX with React).

- You'll be able to target all these platforms from a single C# project. With .NET 5 and earlier, Xamarin required you to have a separate project for each target. This will result in a simpler codebase.
Thanks for responding, you don't owe me or anyone an apology in my opinion and I appreciate that you took the time to read what I said, despite being disappointed with your response.
I take it as self deprecating. Most things people write online is shit- including my comment. Get off your high horse, you aren't special, you're making farting noises online.
I'm referring to this, from the GNU.org license comments page:

> It [the AGPL] is also technically not compatible with GPLv3 in a strict sense: you cannot take code released under the GNU AGPL and convey or modify it however you like under the terms of GPLv3, or vice versa.

In my mind, this is a pretty bad limitation. If I'm writing software for the free software community, it seems bad to me if someone working on a GPL project cannot take my code and use it as part of their project without the whole project then being under a mixed license. The terms of the AGPL would apply to a derived work even if all the other code was GPL. While it might sometimes be possible for someone to do everything they want that way, the added complexity means that using part of an AGPL project may be a non-starter even in those cases.

The AGPL is also not compatible at all with GPL 2, which many projects are still using.
Generally it’s not the auth itself that is the problem but RBAC, multi-factor auth, integrations, etc.

We’ve looked at Auth0 and Okta because we wanted to see if we can save some dev time devising RBAC and supporting a lot of different auth integrations. Ended up doing it in house since the quote was unacceptable (essentially a mid-level dev salary per year)
No matter how fast I type 3 + 6 + 9 into the stock Android calculator (on a Pixel 3a, 2 years old), I can't replicate keypresses getting ignored or laggy, input-blocking animations.

There's also zero lag scrolling through Google Photos. I don't have an iPhone to compare to, but I can't imagine how it could get any better.

If this is actually still a problem 10 years after the linked article was posted, I'd say the main problem is then instead the variety of processing in Android devices. I'd guess I'd see these issues on cheaper phones (maybe I can dig up one of my $79 burners to try with), but I doubt this problem exists on any phones of comparable pricing to iPhones.

Comparing iOS to "Android" might show some clunky/laggy UI in cheaper models, but comparing iOS to iPhone-priced Android phones most certainly won't (most of the time).

[*]: Though, obviously, I expect the sheer amount of variety in Android phones to still produce some expensive, low-power phones that would be an exception here.
Apple must divest iCloud; Amazon must divest AWS; Microsoft must divest Azure, etc. I guess alternatively they could divest their marketplace, exchange and search engine components instead of their backend components.

The goal here seems to be to run up a ton of forced divestures in a “here’s what I want you to do, you figure out how to do it” way.

EDIT: https://www.hawley.senate.gov/senator-hawley-introduces-bust...

Here’s the PR statement out of Senator Hawley’s office, for the summary.
Hopefully a chance for them to take what they learned through years of experience and cut away from the cruft/technical debt that built up with Xamarin.Forms.

I think there is potential for redemption here -- although I do worry the native widget binding approach still comes with a lot of friction that adds unavoidable complexity. However, Maui's new "handler" pattern for native widgets seems like it could be adapted to support Skia/manually rendered widgets if someone wanted to invest in that non-trivial effort.

From my experience the native widget binding is both the strength and the weakness of the approach. You get to take advantage of battle tested native controls that are fully featured. But if the platforms don't have enough similarity between them to create a cohesive interface then you're battling multiple platforms trying to take advantage of the native features layered in another opinionated model that sometimes can be detrimental to the native performance you're hoping to leverage.
Snopes? ok lol

https://archive.md/Wy4GT

https://archive.md/wrEXO

https://archive.is/AqkNf

http://archive.is/HNgc9
Like Product Hunt but for Crypto
That recommendation turns out to be pretty good advice:

https://www.reuters.com/article/us-health-coronavirus-facema...
At those resolutions and frame rates multiview stereo is probably your best technology for the moment.
I suggest you read more deeply into the legal interpretations; it is not so clear cut as you put it.

A more permissive license is simply incompatible with this project's ideals - they are willing to sacrifice developer convenience for user freedom and prevent corporate theft and bastardization of the codebase into competing products
Lithium batteries are high output until they're not. Like the CR2032 battery in my car keyfob it's working until it's not. The drop from 3V to 1V is precipitously fast. Also, 1 year is extremely conservative. I normally get 3 years out of these batteries. An Airtag that's constantly being interrogated may run out faster than say a keyfob used 5x a day
This seems like a problematic situation. In a vacuum I can see how they want to mitigate the stalking risks, but as of right now, unless you have a recently updated Apple device then, then you're completely ignored by the stalking mitigations. There's nothing official from Apple on the Google Play store that would mitigate that situation as well. This just seems like a low barrier to entry stalking tool on the extreme side of use cases for people Apple doesn't have business interests with.
All mac computers except the Mac Mini come with a keyboard and mouse. The Mac Mini 2 USB-A ports, which would be suitable for the keyboard and mouse with USB-A.
Didn't that preaty much out grsecurity into (an even bigger) obscurity as no one sane will touch a logic bomb like this, not to mention build their business on it ?
Look, some of us prefer the base 2, ok?
I think they don't advertise it that prominently for marketing reasons, but note that you don't have to pay unless you use Pulumi SaaS (the web ui).

In that case, you can save your state in an S3 bucket, just like you save your Terraform state somewhere.
It gave me flashbacks to using DOS with Norton Commander :).