skysight-inc/HackerNews huggingface dataset:
> Well, no, only if you’re under the jurisdiction of the EU courts.

That is an awfully naïve argument my friend.

If it were that simple then there would, for example, be no need for a 68 page document entitled "The Sedona Conference Commentary on the Enforceability in U.S. Courts of Orders and Judgments Entered under GDPR"[1].

Allow me to quote from the Conclusion on page 68:

"As the Commentary shows, the enforceability of GDPR orders and judgments in a U.S. court will depend on several factors, including the nature of the relief sought through the order or judgment, the nature of the underlying violation and the process through which the order or judgment was initially obtained in the EU, and the U.S. organization’s contacts with the EU."

I would say that makes it pretty darn clear that it's far from being a simple argument about the jurisdiction in which the defendant is based.

[1]https://www.dorsey.com/~/media/files/newsresources/publicati...
> You truly don't find that hard or complicated?

This is like saying: "You think a 64bit integer is simple? OK, let's dig into the C memory model, twos complement, overflow CPU flags, how CPU caches are implemented, architectural nuances that can lead to unsynced writes from registers to RAM, etc". In reality most people can just learn that it's a number that holds 2^64 values, not complicated. If you want to really understand integers though go read the intel manual and the C memory model specification.

Are lifetimes complicated? If you're a compiler developer who needs to consider the implications across all features and edge cases, yes. If you're learning the language and you just want to write "find me a &str in another &str but don't clone it", no, it's not complicated at all.

The vast majority of beginners can just learn "& means any number of readers and no writers, &mut means one writer and no readers".
> The current trend is that people from nations that were colonisers are the cause of, and are responsible for, the woes of descendants of colonised peoples. It's good to see that you can see through the bullshit too.

What? I don't think that's what the OP is saying at all? If the descendants of colonizers and the colonized peoples have been living in the same country for centuries, what does this have to do with foreign investment in local assets?
Quite modern! A few of the latest features we don't use yet but overall it's pretty up-to-date. Also no exceptions.
> Sure, there's some language later on which allows a province's superior court to order that the house be sold. Be sold. What a punishment! And unless it's some massive televised case, the superior courts don't have time for that.

1. I sincerely doubt that the courts will let the law remain unenforced. Let's agree to disagree on that.

2. The reddit post goes into details (which I agree with) about how this law changes the incentives, so real estate agents, sellers, lawyers, etc. are unlikely to want to aid foreign nationals in circumventing it.

3. Selling is a punishment. Everyone gets fined, the house is sold, and the seller cannot get any of the upside from the sale. At best, they break even (minus the fine).

> Marginal note:Paragraph (1)(c)

> (2) Regulations made under paragraph (1)(c) must provide that no non-Canadian receive from the proceeds that results from a sale of a residential property ordered under section 7 more than the purchase price they paid for the residential property.

https://laws-lois.justice.gc.ca/eng/acts/P-25.2/page-1.html
Upward feedback of executives can work, as I heard an executive rant about how the upward feedback program was a conspiracy against him by his peers, before he eventually vanished.

As others note, feedback that only goes up one level can't really be anonymous.
Manufacturing!

Hoping to get a handle on scaling my business, either through injection molding or just amassing a 3d printer farm; one new printer at a time.
What is wrong with disliking rest? The more I use rest and the older I get the less I like it. Rest always looks so simple at first but then you realize that e.g. the size of the filter clauses for listing some resource exceed the maximum reasonable URL and you need to turn it into a post. And it is also very common that a lot of what you are doing does not in any way match to any easy to grok resources so you just end up with some kind of RPC anyway. I feel I waste too much time on pointless choices when designing Rest API:s and that designing an RPC API often is more straightforward.

Personally I find JSON-RPC pretty meh and do not have that big of an issue with Rest, but I can definitely see the perspective of those who dislike Rest. Rest has it issues.
I'm on the static side. The sanitizers are indeed great tools but they are mostly too performance-costly to run in production environments, so they just exist for your tests and maybe for some small percentage of your production environment. Deployed in this manner, it isn't going to catch everything.

I think that asan is also theoretically unsound (I don't know its innards well enough) based on how it actually tags pages but in practice this isn't super relevant. The question is whether you actually execute the problematic sequence in some build that has asan enabled.

> Not sure if that qualifies for "uber".

Writing C++ code with minimal memory errors would qualify as "uber", given the data available from both academic and industrial research on C++ application development. The data is very clear - real applications run into these issues with frequency even when they consistently use modern smart pointers.
Are the people who sold their houses to these foreigners at a high prices still in the community?

Didn't you benefit from the taxes their windfall transaction generated?
Is your bottle of wine ready for market in 6 months or less from when you plant your vineyard? Probably not though. The speed at which you can get these yields is another huge advantage for these crops. Some commercial growers are having new plants grow up to harvest continuously, with separate rooms for vegetative growing, flowering, and even maintaining a genetic library of clones fit for expanding and out planting in your greenhouse. You can also grow this crop anywhere in the world, unlike grapevine.
What I found strange about MariaDB is that it is ~10 times slower than MySQL on OLAP queries[1]. It looks entirely wrong and most likely related to an issue with Debian packages.

[1] https://pastila.nl/?00697bd3/ef6bf8858182a18150cc646c0c73e65...
Personally, I wouldn't deliberately signal "I'm too small time for you Fortune 500 outfits to bother with".

But even if you don't mind doing so... Our company didn't have any outside-the-US employees - until we did. We hired one remote in Canada, and we hired some contractors in the Philippines and Portugal. So you're creating a situation where either you have to fix your ability to let people connect from outside the US right now (with all the security issues that may cause, which you also have to fix right now), or else you lose a customer each time something like that happens.
SEEKING WORK | Austin TX USA | Remote only (some travel) - part time

Machine learning expert, PhD. ML lead at late-stage startup. Previously only data scientist at company with > $1B exit. More than a decade of experience creating and maintaining ML products for early to late stage startups.

Technologies: Python, sklearn, pytorch, Julia, and so on.

Email: andrew [DOT] rider [AT] gmail.com
GitHub: https://github.com/arider
Linkedin: https://www.linkedin.com/in/drandrewrider/
It always saddens to me when people only think of the extremes, while perfectly good options exist!

If your develop for highly locked device (iPhone) which requires the very latest version of huge dev environment -- maybe choose some other development target which does not evolve quite as much. Qt, Java, etc.. are not updated for years. And don't forget to make sure that your OS does not break without updates either.

Gimp is more clunky than Photoshop, but it will never fail because of lack of license server.

This part is especially annoying:

> At sea, without internet, if I wanted to look up how to fill a polygon, I couldn't do it, but if I had printed it?

.. or maybe you could have gotten some e-books? They take much less space that paper books (important on yacht!) and lasts forever. Postscript format, from 1985, is still readable by all modern systems. Plain text ASCII, from 1968, is still being written every day. Even HTML 1.0 is rendered by all modern browsers.
Facebook got sued a whole bunch. Between the FTC's various privacy-related consent decrees, Cambridge Analytica, and the GDPR, they functionally can't do the whole "push people to overshare" thing anymore.

I will say though, it's specifically the old Facebook mentality that made me hyped back when Google+ was announced. And then it crashed and burned - which was exactly the point in time where I stopped wanting to be on literally any new social network.
The posted article argues against (or exposes) faulty logic, and to do this talks about cashflows but misses the simpler flaw in the argument it critiques.
It is a pretty odd article. Their conclusion is "Parking lot owners think it's not cost-effective but we disagree because solar very cool." with no real justification.

Actual quote is:

> Parking lot owners may forego solar panels for reasons including cost and inconvenience. However, some solar experts think increased interest in sustainability (90% of Americans wanted more solar farms in 2020, according to Pew) could mean more solar parking lots are headed our way.
"Never hand out non-owning pointers or references" is not, in my opinion, an acceptable design constraint for a tremendous number of systems.
How can I find out if one of my photos was used against its license? And then I suppose I can sue them, right?
Clutter Is Good for You
We're already seeing massive searchability problems from the mass migration of communities to discord servers, it's not a good thing and doesn't make anyone safer.

The choice of bogeymen makes me suspect the motivation is insincere, though.
There should be more of this.
I'd like to see someone tackle a PhD thesis (or ten) on applying formalism to the concept of migrations. I suspect there's a missing aspect of type/group/category theory that's at least as big and important as variance is.

I think it might already mostly exist, it just isn't organized into a discipline.
I tried Json rpc, swagger, and json schema for a few use cases at work when we were deciding on our serialization format.

The schema definition in it is really really ugly and I could barely get it to work. Also at the time (2015) the language support for that schema definition wasn't great. I also tried swagger at the time and there were quite a few things I just couldn't get it to do. If I couldn't get it to behave in a targeted research spike it was really going to be a non-starter for new employees trying to slam out features. These issues meant people would go with the losest typing or just "object" for a lot of items. One problem is that they both have the flexibility of XSD but whether a given laganguage will support that validation or do it correctly was spotty at best.

We went with our own dumbed down version of GPRC called Twirp which is very very simplified. The schema language for proto3, which twirp uses, is a lot simpler to write, uses close to just native typing, and does a lot less. Doing less was actually nice because it meant less rules. I was able to implement the prototpe ruby version which someone else (thanks cyrus) put into production in under a day because there were so few rules but what it had gave us type safety.

For years people really liked REST because it was "self describing via api" but it turns out no one cares, what they want is a client in the language they're using that works. They really don't care that much how the client is generated. So to me Interface Description Languages (IDLs) and a code gen step are what you want with some simple basic rules.

We built a similar tool for config checking, and most of the features weren't used. But Twirp and this language removed a whole class of issues that had plagued us and caused outages for years around string vs int in configs and apis.

Also, at our scale, for some services, proto or another binary format has substantial benefits. I'm not saying it matters for your service and human readable is great (we had to learn and built up tools to debug things, and kept json support in twirp exactly for the poor humans), but when you're sending a millon requests a second or so to a service, there is a noticeable cost equivalent to an engineer's salary in infra costs. But most people are not running at that scale.

On the front end GQL worked better for us, it pushed the flexibility to the front end devs while we sorted out the back end over several years. The level of coupling we'd have had if we ran Twirp, Swagger, or anything else direct from front to back end would have made work 100 times harder. I was skeptical when they started but it's been a boon, and I was smart enough to let smart people be smart in an area I'm not smart in eg I stfu.

Anyway TL;DR (at the end of course) there were better options for me such as Amazon's internal one, GRPC, Twirp, roll your own Proto based, and about a billion others.

I'll also note the v1 spec wiki page link is broken.
If you know what to listen for it’s pretty easy to figure it out. Here’s the song on YouTube and the morse code part starts around 2:30. Super cool.

https://m.youtube.com/watch?v=fVUWjoTxOU8
https://archive.ph/xYOqs
Slab | Engineering | Remote (Worldwide) | Full-time

At Slab (https://slab.com), we believe that knowledge is the foundation of any organization&#39;s success. When a team&#39;s collective knowledge is more accessible, that team&#39;s potential is limitless.

Our product helps teams easily create, organize, and discover knowledge across the entire company, from non-technical to tech-savvy. Each day, thousands of customers rely on Slab across their entire workforces, including Asana, Benchling, and Fivetran.

You&#39;d be joining a team of thoughtful and experienced engineers, distributed worldwide across North America, Europe, and Asia.

Stack: React, GraphQL, Elixir, Phoenix, Kubernetes

Take a look at our open roles:

- Frontend Engineer - [https://jobs.lever.co/slab/287fe35f-9e9d-4d5a-a2d5-d1d7fc67c...

- Backend Engineer - [https://jobs.lever.co/slab/e97d694f-2ef9-47e7-8599-c6e624e4d...

A couple of technical posts from our engineering:

- Upcoming CSS Features to Look Forward to: [https://slab.com/blog/upcoming-css-features-to-look-forward-...

- Why we use Elixir: [https://elixir-lang.org/blog/2020/11/17/real-time-collaborat...
It's also illegal to record the expression of consent to start recording!
All of those languages adopt the C-like syntax and semantics, it shouldn't be hard for someone with familiarity with languages in that family to deduce what's being conveyed in code in languages they might not have experience with.
I'm claiming the fundamental underlying demand is for actual housing. Canadian cities are not allowing enough housing to be built for their increasing population, which leads to a price spiral, which in turn attracts savvy investors.

Who ultimately owns the properties does not really enter into the price equation.

I know the stories of how foreigners are so greedy that they buy houses but decide to forego the income from renting them out. Those anecdotes don't pass my smell test. Greedy people like to have income!
The benefits of thinking out loud are massive. So are the costs.

The only way to sharpen your ideas is to find other humans to talk about them with. The subject barely matters - you may be dead wrong or 100% correct, but you can only know once you test it with intelligent people. Plus, you build deep friendships when you're open. I can't tell you how well this has worked for me - better friends, clearer thinking.

The problem is obvious. We live in a judgmental time when it's easy to rub people wrong and lose friends - or even your job. So how do you stay safe?

Protect people (even friends) behind aliases on controversial topics - until you build up mutual respect and trust.

I want to show you what I'm talking about. I'm running a private beta for https://hiweave.com/. If you sign up for an invite, mention Hacker News (I'll put you guys in a group together).
You can also still buy cotton resume paper, although with how digital things are these days I’m not sure how useful it would be unless you really want that Target job.
There's a reason why there are dispensaries for ohioans set up just across the michigan border.
> No self-censorship.

This is a very common belief, but I don't think it's strictly true. Sometimes people inadvertently speak what they're thinking, so an even surer way to prevent being punished for your ideas is to prevent yourself from even thinking them in the first place. It's a kind of defense-in-depth against wrongthink punishment and one I think most people understand intuitively.
The process for removing either is exactly the same.
before we had [a] way to mathematically describe nothing.

This seems a little overstated since positional number systems are fairly sophisticated mathematics - you can deal with 'nothing' without needing zero in its modern sense.
Who are the middle that databricks targets? I thought their product is usually something org wide, hence a near executive level decision. Then again I'm not too familiar with them
said who? the historical context is that REST comes after SOAP, a very clunky implementation of RPC, and positioned itself as different. It got popular because of its ease of debugging.

Conceptually there is another key difference that is REST revolving around standard HTTP verbs and encourages CRUD like APIs while RPC encourages APIs more like a non networked APIs
shoot you're right. Now I need a divorce :(
I’m comfortable thinking in public but less comfortable in personal branding oriented contexts. Remember, there are other avenues than Twitter, with different formats, social contexts and ground rules. Twitter is like the debate club or student council, with the loudest voices, and a narrow Overton window. Combining Twitter’s focus on people and their public achievements with social instincts resulted in basically becoming a social posturing platform. Same with eg LinkedIn. It is possible to operate with different values in any context, but it’s good to be aware of skews, biases and gravitational pull of the medium itself.

In short, don’t be afraid of public thinking, but pick a platform that aligns with your values and goals.
Big Trouble in Little Interconnects
What have you created personally, that give you the right to want to destroy the creations of others?
I wonder what's the impact or Airbnb in big touristy cities. Has it been quantified somehow?
The author mentions power use being a factor. Last I did some research into this, smartphones are by far the most power-efficient general-purpose computers broadly available, using several times less power than something like a raspberry pi. I wonder if running an open-source OS on smartphones was considered for their sailboat permacomputing?
Use a private group chat, and it can be decentralized too using matrix!

The fediverse is a public protocol, and indexing public content is fair use(ML is not indexing, its very different), so any kind of licensing won't matter.

Discovery is already crap in mastodon and the fediverse in general, please don't stop people from improving it.

It may look like eternal September for fediverse natives, but that's what going mainstream is like, don't like it? Create something with some kind of intentional barrier like HN to stop the masses from joining.

I find the fear about getting doxed and having your words watched and used against you from fediverse natives very funny, because I guarantee you that most of them support cancel culture.

In general I find old fediverse communities too fragile, one example are the crazy content warnings(just mute words and topics you don't like, simple!) and now this.
I have been living in the fediverse for years and have adapted this strategy I think can work for most people:

-I have a real ID account with my picture and link back to my domain web page. I approve the followers to keep it to mainly people I know and trust. I post mainly to followers only or post publicly rather mundane information that I would not mind coming up in a deep background check.

-I have another anonymous account where I am most active and can express political and other views publicly without worry. I tell some of my friends of this account to follow after they have found my real ID one.
> if the Minister and provincial superior court can be bothered.

I know that for immigration and citizenship cases, officers at the border are called minister's delegates in certain contexts: they do things that the law authorizes the minister of immigration to do.

It's not like the minister has to get personally involved. It just means the ministry is in charge of referring cases to the court, so they will create an office and hire a bunch of bureaucrats to do this.
Keep learning how to catch rabbits (users)
So are all humans if you want to keep looking backwards. I presume you know the real point.
> soap scum in hard water areas

I have a question, I live in a soft water area so I'm not familiar with the problem.

Would you have the same issue if you were using vegetable oil-based soap (e.g. Marseille soap, Castile soap etc.)? Or is any type of "fat" going to cause the same issue?
> Exceptions in all but name.

In particular, checked exceptions.

This is a very interesting article that discusses the isomorphism between checked exceptions and error return types, they ended up with checked exceptions where a function Foo that may throw must be invoked with "try Foo()" - very similar to Rust's ADT-based macro/syntax.

https://joeduffyblog.com/2016/02/07/the-error-model/
Most of these historical disruptive technologies seem to affect only a relatively small group of professionals or then small part of human skills. Therefore there are not too many people complaining and also most of these people can find some new jobs, perhaps after retraining.

On the contrary, AI could affect large groups of professionals and large (if not all) part of human skills. The protests opposing AI might then be completely different scale than the previous protests.

Also the an individual losing their job would suffer more since there might be nothing they could do, even after retraining, that AI couldn't.
we've worked very heavily with the pyright developers directly on some aspects of SQLAlchemy 2.0, namely the new dataclasses feature : https://docs.sqlalchemy.org/en/20/orm/dataclasses.html#decla...

that said, the codebase primarily targets mypy for internal type checking; we tried targeting both tools simultaneously but there were great differences between both tools, which tended towards doubling our workload in getting everything to pass typing fully. In more than one case there were areas where the two tools would mutually disagree with each other, making "correct" typing impossible. This was some iterations back and mypy has had a lot of good releases since then (pyright has had many more, obviously).

when typing a large codebase, there are invariably lots of areas where you just need to "type: ignore" or otherwise do some non-ideal workarounds. it's in that area that trying to target more than one type checker at once gets to be really difficult.
"some jobs would be up to 50% less if they paid quicker"

Why would you give someone a 50% discount for faster payment? Is your cost of capital so high?

Maybe I can pay you advance (with the 50% discount) and then, 100 days later, collect 100% from the customer?