skysight-inc/HackerNews huggingface dataset:
Hollywood is a counterexample, I'll grant you that, but I'd argue it's only because the nature of film making - with many short-lived independent productions - doesn't give unionized work units the monopoly control they would have in large stable production facilities, like factories, and moreover, due to being cultural work, is very difficult to outsource.

Numerous industries in both the private and public sector have declined since being unionized.

Germany seems to have strong unions and a strong auto industry, but the German economy as a whole has suffered decades of wage stagnation. One outperforming industry alone doesn't negate the broader correlation between restrictive labor laws, and degraded economic performance.

>>The free market relies on free association, equal footing, and complete information for both parties.

A free market merely means anyone is free to offer their products/services, and everyone is free to take the best offer on the market.

There are plenty of market failures and government-imposed market distortions, but the idea that locking the market down with one-size-fits-all labor relation rules is going to mitigate the harm of these distortions is unbelievable. It's just going to make industry less effective, and in the long run, less beneficial to its workers.
reminder that NIST should not be trusted given their history with regards to standards around vulnerable crypto as well as potential for manipulation due to "higher level" .gov organizations:

https://projectbullrun.org/dual-ec/vulnerability.html
No one wonders
I really wish the people that downvoted you had the maturity to respond with their (presumed?) rebuttal; I know little about the topic and was following the conversation with interest, but I have no idea of whether this comment's claims are sound or not, given the juxtaposition between the lack of responses and the downvotes.

I mean, now I'm going to look up what I can about the topic, but it's just such a frustratingly immature habit that lowers the quality of discourse here. /rant over
So it's protectionism?

It's way easier to teach someone to code who is already really good at manipulating/modeling data than the other way around, IMO.
SQL is pretty great. I've been doing advance SQL in Postgres and BigQuery for quite a while and it's one of the most satisfying experiences.

Once you wrap your head around basics such as GROUP BYs, JOINs, CASE statements etc, you move on to advance concepts such as Window functions and there suddenly a new world of possibilities opens up to you for analytics! I've dabbled a bit in PL/pgSQL, but the syntax is way too arcane.

SQL can also be counter-intuitive sometimes. I rewrote a particular PG query and reduced time from ~30minutes down to 2 seconds by adding a subquery. :)

And no, ORMs can't really do what SQL can do in an equivalent manner.
Systems for Spreading
I've been coding in Python and Ruby most of the time and now it's Ruby with Go. And while I agree that autocomplete is less usefull with Ruby due to it's nature - it saves a ton of time while developing in Go. And sometimes you simply don't have any documentation to reference. So it's 'go to definition' and autocomplete all the way through.

1. What's the problem with it being Dockerized? I have my current project Dockerized too. JI just have :volumes in my docker-compose for development. If source code access is what we are talkig about.

2. see the above
> Now, it feels like that creative energy is flowing through Minecraft-like games and massively improved freely available game engines.

Is it really? I play a lot of strategy games on steam (civ, stellaris, crusader kings 2, eu4) and they seem to have a wealth of mods available.
> why employer would employ "commodity devs" who are part of the union, and why devs, who standout and have a leverage would option to join union?

The parent poster answered that question for Hollywood. Union members (and here I'm speaking of SAG-AFTRA, which represents actors) are not allowed to work on non-union productions. Union productions, which encompass almost all major studios, are required to give first preference to union members and only hire non-union members when they are of "essential skill and quality"[1][2]. A non-union member who works on a union production has 30 days to join the union. If they do not join, they can't work on any more union productions.

Since all the big name stars are union members, big studios have to have union productions in order to be able to hire them. Stars make plenty of money regardless of whether they're in a union or not, because their agents negotiate well for them.

But most stars were once unknown and so they had to join the union when starting out, in order to be able to book gigs and build their career. For a millionaire actor union dues aren't a big financial hardship, and union membership doesn't affect how much money they make now. And they need to maintain union membership in order to continue working on union productions with other big stars.

A game industry union would probably work the same way. An employer would be forced to give first preference to a "commodity" union dev if they want to be able to employ the star producer or designer on their production. A non-union commodity dev has to take union membership after getting their first job offer else they can't work on another union project.

It would also probably mean that game industry jobs become like entertainment industry jobs: you're hired for a specific project and you move on when it's finished - instead of being like the rest of the white-collar workforce's model, where you're hired at a single company and build a career there.

1. https://tvtropes.org/pmwiki/pmwiki.php/UsefulNotes/UnionsInH...

2. https://en.wikipedia.org/wiki/Taft%E2%80%93Hartley_Act#Close...
Can you list some journalistic outlets that don't do this? Because I can probably find articles by whatever that outlet is that mangle stories to fit business, political, ideological, and other interests. Even when unintentional, stories that depend on complex information are often dumbed-down and result in incomplete, inaccurate narrative. Not to mention the benefit of hindsight, and important sources whose additions or subtractions substantially change the result.
Pilot unions still exist even for these regional carriers. How has collective bargaining worked so well for 737 pilots but not for a regional pilot?
I would actually go ahead and say that his gadget reviews are wishy washy, too soft and lacks objectivity. I understand its not supposed to be a full technical analysis but he makes what makes it popular and wide appealing. Especially, his audio gear reviews are full of subjective claims - "It sounds roomy, with crisp highs and thumpy base but not too muddy." They are, to me, utterly and completely useless pieces of information.

I'll go and read Anandtech now. I don't fully blame MKBHD. I blame the entire genre of youtube reviews. I need data. I need A-B tests. I need technical specification verification using proper metrology. That's how my brain evaluates things I want to spend money on.
AAA is more like the old Hollywood "cast of thousands" films, like Ben Hur. You need a lot of people, but no individual contribution stands out. The overall look is determined by the art director: so you need only a few experts at the top.
> On the other end of the spectrum are the influx of "data engineers" with basic to intermediate knowledge of HDFS, streaming data or various other NoSQL technologies. They often know less about raw SQL than even junior engineers because SQL is below their high-power big data tools.

I always ask a basic SQL question (involving sorting/grouping and one simple join) in my interviews for backend and/or data. IMO if you are calling yourself a Data Engineer and do not know SQL, then you haven't really worked with data, you've mostly just worked on data infrastructure.
Uncle Sam to its friends: Buy technology the easy way, or the Huawei
The thing is that most of the applications do need the complex data and thus do need need deep SQL knowledge. This is why NOSQL (I think) databases became popular. A DBA is called an "administrator" for a reason - most of the time he spends making sure the data is replicated and backed up/restored and really you need her help when things go to shits. It happens a lot but still in the majority of cases her role is invisible as the devs are trying to abstract the persistent layer (Hibernate and all other ORM frameworks, for java for example) where SQL-compliant database are just a part of the corporate landscape - not because I need it, but because it is there and all the mentioned processes are there.
I find cypher to be a superior language to SQL. It expresses relationships more succinctly and intuitively, and has better support for aggregations.
These competitions also take time. SHA-3's competition was announced in 2006, and the final standard came out in 2015. By comparison, PQC was announced in 2016, and NIST expects the final results to be out in 2022-2024. We're likely a decade away from PQC to be moderately widespread in implementation.
> Not even Andrew Carnegie agreed with this take.

So?

> He was an ardent supporter of heavy estate taxes

Yeah, so what?

Heavy estate taxes are a not-horrible band-aid over not adequately taxing the income of rich people as income, but it's better and simpler just to tax income appropriately.

The fact that some rich people like heavy estate taxes doesn't really change that.
Your advice is pretty good, but I would definitely say that SQL doesnt have a strong relationship between lines of code and runtime, you can line break (and many do) your wide table's select into many columns and get there pretty quick.

If you are writing SQL regularly, understanding the basics of how the queries you write is not that hard for you engine of choice, and everyone should be required to understand the basics of reading an execution plan so they can find the right inflection points between data gathering and processing.

I regularly sigh write and maintain SQL procedures that are >10k LOC, and their runtime never would exceed minutes, much less hours.
With all the data scientist thought pieces out there, I really wish there was more in-depth discussion of SQL and highlighting of the other shenanigans you can do with query optimization, subqueries, and even analytic/window functions. (although that last one is apparently the Hello World equivalent in data sci: https://twitter.com/minimaxir/status/1094430576092704768)

As a data scientist, I spend a lot more time building queries than working with models.
Is CSS Modules considered to be "CSS-in-JS"? It does require JavaScript to import the class names, but the stylesheet itself is static. I personally find it to be a great solution to the scoping problem, and combined with Sass it's very flexible. Even theming is a cinch with a single shared Sass file with theming variables, or CSS custom properties.

Every CSS-in-JS library I've tried makes everything way too cumbersome with no real upside. I especially hate how they all spread my style declarations all over the place.
>Should a hospital expect something different from a "unionized Nurse" instead of a "non-unionized Nurse?"

While nursing certainly chanes over time and is a difficult job, a good nurse from a decade ago could likely get up to speed within a week or so.

Given the pace of change in coding, I don’t think ai could say the same for a decade younger version of myself.
What is magical and mind-bending about `amb` is that it rewinds through arbitrary complicated call stacks, similar to an exception. This is why it's necessarily a special form.

The Haskell version requires each callee to be annotated with the `Amb` return type. It cannot be used to escape unless the caller is prepared for it to escape. That's a significant limitation (but all we're really saying is that Haskell doesn't support call/cc).
If raw speed is not an issue you can always fall back on temp tables or a cursor for those cases where you might have extracted an initial dataset to then iterate over.

EDIT: A CTE (Common Table Expression) might be what you're thinking you need. You can do some fun recursive queries with them.
Dr Bernard Peuto, the Architect of the Zilog Z8000 Processor Has Died
All the .NET projects I have done on the cloud have been deployed on Amazon EC2 instances.
Singapore: $61,751 S. Korea: $32,777 Chinese Taipei: $25,999 Russia: 12,000 People's Republic of China: $10,000 India: 2000

It's crazy how successful Singapore is given it's small land mass and multiethnic demographic. I used to say Singapore is Vancouver, BC that made it or the Utopia that South Koreans dreamed of becoming in the mid 90s.

Korea also done good, Park Chung Hee managed to whip up the South Korean economy using the Japanese system but later became more authoritarian as the economy expanded, people started demanding more freedom. Unfortunately, he was whacked by the Korean CIA.....I don't know how obvious they need to make it, hiding in plain sight....

Chinese Taipei falls behind Korea by nearly 70% of China's income...I'm shocked I always thought Taiwan was richer because I remember in high school in Canada, they would drive BMWs and street race with modded import cars....although nothing compared to mainlainders with Lambos and Ferraris

As predicted Russia is right down there with China, but thanks to oil and arms exports they have a recession proof residual income and nukes for a rainy day.
Does this mean the app is necessarily a trusted component here? What's to stop an adversary from reverse engineering the application, especially on a platform like Android where applications are side-loaded and binaries largely maintain source-level semantics?

I guess you could argue that, from the merchant's perspective, they just want to avoid being the easiest target.
Unity is c#

And the c++ of a decade ago is quite different from today.
Cloudflare | Kubernetes Software Engineer| San Francisco | ONSITE | FULL TIME

We are looking for senior engineers to help build and scale our Kubernetes infrastructure. K8s experience isn't mandatory, experience in other similar cloud/container infrastructure projects could be transferable. Should be comfortable writing and debugging code, Go is a plus.

Come join us and help build a better internet!

Apply at: https://grnh.se/346e4b521
> A CVL beam machined a 20-mm hole in the tip of the drill.

I could do that with my .45acp at 10yards
You were nothing less than polite in your remarks. I appreciate your (edit:) candour, you have absolutely nothing to apologise for.

My handle is significant to me, and AFAIK there's no way to change your handle on HN. Though being honest, even if I were given the chance, I probably wouldn't change it.

I'm unsure if there's a mechanic to block some one on HN but if it does, I'd recommend you use it in this instance. Apologies that I can't be of any further help.
Members of the acquired company had a 7 year run between King and Activision, so not sure it is fair to attribute layoffs to either acquisition.
> to get that wrong at the air carrier level speaks to an incredible failure in training and evaluation

The problem is pulling up in case of a stall is the natural, intuitive thing to do. In a high stress situation, one is liable to revert to it. This behavior is the cause of many, many crashes.
Te Koop Munstergeleen, Houbenlaan 2a
I'm surprised a Berkeley survey would neglect to mention PiCloud, which may be defunct but cloudpickle is still used heavily today (e.g. in Spark). The paper also appears to neglect the issue of code deployment, which can be a major undertaking and hidden cost of any web-based application, especially if the app has particular system dependencies.

There are (private) solutions out there for moving parts of running JVM programs across machines. Wouldn't one expect a forward-looking view of Serverless to encompass serialization and transport of the compute environment?
Isn't the B-class that Tesla was involved with the one that was discontinued (in 2017) after selling fewer than 4,000 cars? http://www.thedrive.com/sheetmetal/13097/mercedes-benz-disco...
Fair enough. For questions, Stack Overflow is what they usually point to. Sometimes GCP staff logs on and answers, otherwise the community.

For the refund scenario, I found this: https://cloud.google.com/billing/docs/how-to/resolve-issues

You can also vent in their feedback widget within Console. To my surprise the product managers actually read it, and sometimes respond back for more information.

There's also a UserVoice forum to voice out feature requests for each product: https://googlecloudplatform.uservoice.com/forums/299943-goog...
He lets a lot of weird behavior slide. Like this one:

"Under the simple pay-what-you-wish variation, 8.39% of people purchased a photo (almost 17 times more than before), but customers paid only $.92 on average.

The final option — pay what you wish, with half the purchase price going to charity — generated big results: purchase rates of 4.49% and an average purchase price of $5.33, resulting in significant profits for the theme park. This is a substantial result, especially since it came from a real setting."

Why does pay what you wish with half going to charity slash sales in half compared to standard pay as you wish?
220 Comments, I still don't see any one with good enough rational reason for removing jQuery. If you are reimplementing more than a few jQuery stuff to make it work then it shouldn't have been removed in the first place. At least not now.

And now they are dropping IE support, jQuery, which defeat the purpose of these framework in the first place, making it work across multiple browsers.
This is an example of correlation != causation. The French Revolution, commonly cited as an example of this, was not caused by wealth inequality. It was caused by the fact that the French were practically, in some cases literally, starving while the government flailed about ineffectively, accrued tremendous debt seemingly to no end largely driven by fruitless wars, and ultimately turned to taxation to try to sustain a failing state. It was not an otherwise comfortable people suddenly deciding to lop off people's heads because wealth inequality rose beyond some acceptable level.

I doubt we'll ever see another effective organic revolution in any developed nation because people in general no longer have the chutzpah for the actions required to change a government that doesn't want to change, and because we've all become contented from that pale white glow in front of our faces for ever longer fractions of every single waking moment. There's also the effective division of society. Two sides increasingly hate each other which means if either side ever crossed that invisible line, the other side would suddenly become hugely pro-government.

There are also some economic changes that mean France's situation would never be replicated in a place such as the US. In particular money no longer has any real meaning. It's not backed by anything and governments can 'print it' (not how most money is made, but that's another topic) to no end. The only real constraining factor is perception. So long as your people and other nations agree to believe your money has value, then it does. This is how we can spend trillions of dollars we don't have on wars, be $22 trillion in debt that nobody expects will ever be paid off, inject huge sums of money in the market to artificially inflate it and call that 'growth', yet still have an ultra-premium rated currency.

This is also why 'helicopter money' [1] is thought to be a good idea * . You print money, load it up on a helicopter, and then drop it down to the people. The asterisk there is because it's a good idea only if people don't expect it to be repeated. It all goes back to perception. Keep dropping the helicopter money and people stop believing in the value of the dollar and so it indeed loses all value. This is, as an aside, a major issues with things such as a basic income. We could easily 'afford' it. But you very much are risking a perceptive change on the value of the dollar with such systems in which case all that money you're tossing around becomes worth about as much as the beads at Mardi Gras. And tossing even more only trends towards hyperinflation.

The point of that aside on money being that France lived in a time where there was a fixed amount of money and their government was wasting that money. Today our governments waste money like never before but it has less effect on the common people since governments don't need the amount spent to be less than the amount 'earned.'

[1] - https://en.wikipedia.org/wiki/Helicopter_money
Thanks for the link. I meant in a more narrative sense though. I like to imagine that some fool cut down a tree and changed his or her mind and tried to stick it back together and lo and behold it worked.
Notes from a 1984 Tech Talk About Programming Languages
If you're mathematically minded (really just basic set theory), maybe try learning relational calculus. You'll express database queries in terms of Cartesian products, selections and projections. These operations translate directly into SQL, so maybe it'll help you think clearly first, then apply the syntactic translation. Honestly, if I had the choice I'd rather just use the syntax of relational calculus, as I find SQL too verbose and convoluted.
I’d add LATERAL JOINs to the list.

For those unaware of LATERAL JOINs, it’s like a for each loop in SQL. Blew my mind and opened up so many possibilities.
I was talking about the funding, not the valuation.

They are presumably looking for a way to sustain themselves, but I still don’t believe they’re “desperate for cash”
SQL has opened a lot of doors for me. It's a starting point, not an end though. Learning about dictionaries, lists, and other data structures has proven valuable and compliments SQL and tabular datasets very nicely. I got into those areas by working with SQL generators (ORM's) written in Python (airflow).

My thinking on SQL has evolved and lately I see it as a set definition tool. "Do action X on dataset Y." It's really useful for understanding data structures and data meaning too.

I've worked with more than a few SDE's who look down on SQL, but it's a really good tool when used properly, and it cuts across many technologies. Writing code to write SQL can be very powerful. And sometimes coded or scripted data wrangling without SQL is very useful too.

15 years ago SQL knowledge was not that widespread and it was easy to get tagged as a report writer. Today, a lot more business, product, finance, and accounting people are really strong with SQL, and rely heavily on exporting data to excel for further analysis. Knowing how to answer business questions, get insights out of the data, and define or categorize sets of data are all enhanced by SQL. Report writing is not as much of a thing anymore because people want to view the data in diverse ways.

The barrier to entry is low with SQL, but learning it well takes time and some mistakes to get efficient and precise with it. 15 years later I am still learning new uses for it. One example is JSON querying and transformation which is supported by hive, presto, and some other compute platforms. It's easy to mix and match JSON, arrays, and tabular data structures, in one or more tables, from the same SQL query.
It was fun watching car spares shift to mini-spares, and now many high-end cars don't have a spare.