skysight-inc/HackerNews huggingface dataset:
See, I don't mind it.

Twitter and Facebook are HORRIBLE tools to rely on. They spread more wrong information than right information.

If free speech is going to survive it will require open systems and responsible journalism. Twitter and Facebook are tools that promote neither.

Bad information, I suppose, is better than no information… but damn have we regressed in a lot of ways.
And other people love chasing new shiny things. I'm yet to see another language ecosystem that solves 99.99% of the problems one might have the way CPAN does.

Would I write an API in perl? Nope.

Would I write something that massages the data that APIs spit out and processes it, drops into a queues, generates jobs, etc? Absolutely.

Mostly because I will write a few hundred lines of code for existing CPAN modules to solve the problem that I have, letting me to move on to doing something else. I like boring tools that just work. In 99.99% of the times the tools/whatever you are writing is not inline, does not need to have amazing performance. It just need to work and be braindead simple. Perl excels at that. I still daily use code that I wrote over 25 years ago and modified it a couple of times since that point ( integrating git ).

Edit: Can't reply below so I will reply here:

Re: I would not write an API in perl.

> I see you have not tried Mojolicious.

I have seen it, tried it, got excited about it and immediately came to my senses because I asked myself "Why on earth would I build or advise people to build an API in perl? It is slow. It is bad for concurrency. It probably has a pile of corner cases that I'm or some other people are going to discover. If I need to ingest something via web I will throw a simple nodejs app. Millions played with it actively in a "web" sphere, and hit most of the corner cases. There are thousands articles on stackoverflow and we have dozens of skeleton servers that already have all the needed foundations, including federated databases that support live password changes, traffic sharding, online promotion and switches, dynamic reloads, do-at-most-once queues, do-at-least-once queues, etc etc. Why would I want to reinvent all of this when the job of the API is to get the stuff and if the question cannot be answered via a couple of lookups push the request to a worker?"

Re: CPAN in 2019

> n 2019, I can only think you haven't looked around much recently.

Maybe. I have not seen it to be the case two months ago.
This should have happened with Python 2/3.
It was cool but by the time I got to the part of people’s accomplishments I felt utterly worthless and left.

God damn, I haven’t accomplished much of anything in my life except writing code and accumulating money to spend on making more money.
"On average, women get 364 weeks of life than men"

I think this should say "364 more weeks".
Thats a valid point.

But don't you think the more features it has the more instances of it will sell?
There's also that nasty Electoral College thing that makes the presidential election effectively 50 sub-elections. That requires each candidate to register in each state to get on their ballot. No doubt, there's fees for that.
Clojure has a focus on concurrency, is functional and it embraces JS and Java, the dominant platforms.
I'm not sure I agree. It reminded me of certain "great" textbooks that sometimes get recommended by experts, that aren't actually that great for someone learning something for the first time. They get the reputation as being "great" because they are great for people that already have a good basic grasp of the material: They are precise and pithy, and they contain insights that are deep and useful, but hard to appreciate if this is your first encounter with the material. (Kleppner & Kolenkow would be a good example of a freshman physics textbook in this category.) It seems to me that maybe the ZeroMQ Guide is in this category. Which, of course, is a noble and important category, but maybe not the most important category if you're just starting out on a topic.
This is why there is a tradition of skull watches:

https://www.watches.com/blog/skull-watches-over-time/
Is this the sinking, tremor feeling you get after your awake state, but before the sleep state? That weird limbo where, if your brain jolts back on from this state, it's as if you awoke from a dream - even though you only dozed off for a couple of seconds?
Whats the joke I'm missing here?
I'm with you, but this is a really poor way to engage with people.
For the record if anyone didn’t know, they ran the software against the state politicians. It misidentified 26 (I think) state politicians as existing criminals. Which I see irony in there.
Is the might of Amazon engineering really behind it though, or is that might behind a bunch of different things of varying importance. How much might can Amazon really bring to bear on any one project?
I'm specifically asking about instagram staff because desktop instagram.com is embarrassingly buggy when it comes to basic core functionality such as the initial display of comments, and loading more comments using the plus symbol.
Most people using the cloud aren't really that cost concious. EC2 is about 8x the cost of bare metal...

If you factor in operational cost AWS can be cheaper but often isn't really.
WebAssembly is developed by the same corporations that own JavaScript.
Perl 6 is WAY more different than Perl 5. Python 3 absolutely should not have been renamed.
Huh? What do your acquaintances do then for 8 hours, sleep?
True. But the concept is just so...
Surely. I have seen too many carriages drive by.
Spacy, the new kid on the block, is in python...
I like that idea, though I'd probably word it differently. Personally, I do spend 2 hours a day 5 days a week commuting. However, I don't commute by car.
What utility does Perl provide in a world dominated by python?
I think a lot of SaaS companies end up failing fast when they focus on the enterprise. The sales cycle is longer, and having a massive client can end up putting their individual needs over features that would make the product more attractive to the market as a whole.

SaaS makes the most money when users can self-service in large numbers at relatively low transaction costs, which typically means SMB should be your first market. The enterprise channel is where you go only once you have a mature product and a healthy revenue base to do the enterprise payola scheme with consulting companies.
Everyone sing with me now: "Correlation does not imply causation!" :D
In a war situation you don't have access to facts until after the dust has settled and the bad things have happened, so two years from now I will revise my assessment of the situation based on "the facts". The facts we do have available are historical record of what happens when self-interested, oppression happy Turkish dictators decide that a group of people are terrorists https://en.wikipedia.org/wiki/Armenian_Genocide
> The Department of Labor's Wage and Hour Division (WHD) is responsible for enforcing the Fair Labor Standards Act (FLSA). The most common remedy for wage violations is an order that an employer make up the difference between what the employee was paid and the amount he or she should have been paid.

> The WHD conducts investigations as a part of its enforcement of the FLSA and many investigations are initiated by worker complaints.

Not only that, but it can go beyond civil actions:

> Employers who willfully violate the minimum wage or overtime laws are subject to civil penalties of up to $1,000 for each willful violation. Willful violations of the FLSA may result in criminal prosecution and the violator can be subject to a fine of up to $10,000. A second conviction may result in imprisonment.

https://employment.findlaw.com/wages-and-benefits/how-to-rep...
Are SaaS businesses really customizing for high paying customers? They may build new features which are then made available to other businesses but I would be surprised if there are separate source trees.

The other issue is that a "great business" and "scale" are not synonymous. In fact many of the current batch of companies of great scale, like Slack, have spent enormous amounts of money to get there, and still lose money after becoming public. Then you have a company like Atlassian, with a confounding mix of enterprise products that are hard to use: but a fantastic businesses that's been profitable since the very beginning.

I do agree with you that the APIs, webhooks, and Zapier integrations solve the problem of customization, although I'd still say it's less customization and more a bevy of options.
I think you're looking in the right direction.

Speaking from anecdotal experience with online communities, when idling or toying at home during their free time, people actually engage socially with friends through chats, networks, games — pick your entertainment drug. They're everything but alone, and it's genuinely real if limited cognitively compared to a real physical interaction.

If you add voice chat to that, at the end of the day you really feel like you spent X hours with friend(s), there's just no other way to put it except for the physical location.

It's almost a given to me that with appropriate videoconf wall-sized (real-world size) screens in all living rooms, we'd just "invite" friends this way most of the time unless the physical interaction was necessary. Less maintenance, less friction to just spend a cool quality hour.

The 'effort' required to move out of your house is getting increasingly higher, your 'local maximum' would essentially converge to an actual maximum in a perfect virtual reality (of which the "80%" / good enough might be just around the next decade).
It’s the Perl culture, to do even simple things in the weirdest way possible and everyone will call you a wizard. Whereas the Python community praises complex ideas expressed as simple code and frowns on tricks. That’s why all but the the most obsessive have moved on. And from what I’ve seen Perl 6 takes it to the next level.
Windows, iOS
From what I could tell, Raku appears to be from Rakudo, the Perl 6 compiler, which is a shortened form of rakuda-dou (="way of the camel" in Japanese). Rakudo also means "paradise". The "raku" from "way of the camel" means "camel", while the "raku" from "paradise" means "fun" or "enjoyable" (or "music").

Incidentally, it also happens to sound similar to "roku" (="six").
Your points are mostly related to the Chinese internal politics. Even if we look away from their human rights abuses, say because the US also has a bad track record, China's using their economical power to bully other countries and companies into self-censorhip and ignoring those abuses. They're essentially trying to legitimize their unsavory actions, and they're at least partly succeeding.

So they are harming our democracies, never-mind their citizens.
You're confusing "checklist-driven development" with developing needed features. I'm guessing because you assume that the features actually work. The problem of enterprise software is less that the features are unnecessary, and more that they work only on paper, but not in the real world. Since the software is sold to people who aren't using it, they can't evaluate the actual implementation and usability - so what gets sold is garbage that meets criteria.

Now what I see you arguing for is not "consumerization of IT", but infantilization of IT. Modern UX is oriented about dumbing down software, removing necessary features because they're "unused"[0], and about a myth that you can eliminate training time. Which is why people - again, not the users - buy into it. The sales strategy is: put it in the cloud, ask for subscription while screaming "it's OPEX and not CAPEX", and remove any and all features so everything looks slick on the demo, and the problem only becomes apparent when somebody tries to actually do something with it.

And then actual users have to suffer. For as much as software is eating the world, I wonder how much actual, hard productivity does the modern software of the web cost, compared to the software it displaced.

--

[0] - The way "data-driven" approach would tell you that there's no point adding airbags to cars, since almost nobody uses them ever.
Had they done it fifteen years earlier, I think Perl could have been the language to learn for Data Science. It still is a fantastic language to slice, clean up, and extract information from text files, and it was already very widely used in bioinformatics.
Thank you for the feedback. Yes, the tour isn't perfect. I'm using a library called vuetour. I don't like it and am about to replace it.

I will resolve the issue this weekend.
Not only parallax, mirrors reflections are also 3D.
What I Learned Working with NASA on a Robotics Project
Nice, posted that when I came across:

> Kubernetes stores the data in plaintext in etcd, a database where it stores all configuration data

Just finished reading the article.
This is not an original idea: https://waitbutwhy.com/2014/05/life-weeks.html

But I don't see credits anywhere.
Note: most of comments are already the usual conflict iOS vs. Android.
Generally yes, but they can wait for Elasticsearch to implement them and port them over with less time/money spent.

I don't think they have a ton of incentive to surpass Elasticsearch, but just to lag behind at some reasonable rate
.. in the old guard of language technology research I guess, because in my NLP lab, no one knows the first thing about Perl (everything is done in Python)
Thanks for the sources!
The docker comparison is apt. Red Hat did take home dockers work and did their homework with Podman, as a result, you basically get a complete docker compatible workflow, but now your containers don't have to run as root and you don't need a daemon constantly running on the system. The organization who really knows Linux inside and out made the better implementation.
I worked in this industry with blackboard, making something similar. The truth is that the school administrators hold the purse strings. They also don't actually have very much money to begin with - margins are tighter because your price per user is much lower than most business to business end-user systems.

The users absolutely want features. And you hear about them. Its the joy of the developers working on it to actually deliver it to them. But the admins don't care. They don't want user-level features and ease of use. They want reports. Lots of reports. They want a system that will generate a report on anything, in exactly the format and UX that they desire, ad hoc. And then they want it to be customizable in every way possible. This is where the majority of work goes, because the people with the purse strings demand it. If they demanded a better UX, they'd get it, and the developers working on it would be MUCH happier. We had one of the "better" UX's but it got older, and work couldn't be prioritized onto it.

So really, the parent definitely rings true to me. The incentives from the "buyers" is NEVER about a good UX. Its an afterthought. Maybe if the buyers were more accountable to those having to use it this would change.
Heaven forbid you make a configuration change that triggers a blue-green deployment and during the deploy one of the AZs runs out of that instance SKU. Your deployment has halted until you can get ahold of AWS support to get them to unstick it (this takes a couple days even with enterprise support). There's no way to know if the AZ has capacity or not, it's something you find out in the deploy.

The workaround AWS support proposed was to reserve 2x capacity so we wouldn't run into this issue on subsequent deploys.
Hilarious, thank you!
They later quashed it, so she got it cleared up eventually. But I imagine this would have been resolved much quicker if she just showed up in the first place.
You referring BBC as a safe source.
I offer you to watch this whole video. You may see how prejudiced BBC is.

https://www.youtube.com/watch?v=QdRIr0QFOqk
> she was charged with, well, not providing proof of payment.

How is this not guilty until proven innocent? You have to prove you paid, otherwise you're assumed guilty.
Lots of (most?) companies will eat some cost to simplify their company/organization.
Agreed, this article captures my experience accurately as well.
fckgw-rhqq2-yxrkt-8tg6w-2b7q8
I absolutely believe that removing it from gasoline is a big factor, but I think it's often over emphasized in the context of today.

Cleveland has twice the prevalence of lead paint over any other big city in the united states, yet has 25% lower violent crime prevalence than say, st louis, baltimore, detroit, and memphis.
Training is already a line item and comes with the cost of the software. "Good" or "easy" training isn't valued as compared to the feature checklist, and it never will be. Unless the buyers of the software are accountable to the users of it, not the other way around, nothing will change.
Junk mail disguised as official correspondence – how is this legal?
I get an error visiting the page :( It it only me?
You're assuming that the cost of human capital actually matters in big corporations. As someone who has worked for several Fortune 100s and a couple of government agencies, I assure you, that is not the case. Employee time is treated as having no value, and things that damage the efficiency of employees are not relevant.

I once saw a "cost saving" round prohibit our team's QA engineer from getting a new SoapUI license (we were supporting an API!). It took three five-person meetings to get official approval to buy a $100 license - at a human capital cost of thousands of dollars. Not an eye was blinked at this absurdity.

Along the same lines, I once saw a lead architect go through the same nonsense to get a $100 Adobe Acrobat license (at a government agency). He said to me "It's easier for me to spend $100,000 dollars than to spend $100". He could have asked for a couple of new heavy-duty Unix servers with Oracle, and gotten it approved easily. But Adobe Acrobat? No, that's waste!

See also "bikeshedding".
Re: coq, Alloy and TLA+ (to an extent) are built around model checking and SAT solvers, which are better at finding problems in specifications.

Coq is a proof assistant (and dependently typed programming language); more aimed at theorems.
The managed ES service makes sense for small things where the operational costs of self managed dwarf the overhead. But at scale, it just doesn't make any sense.

EC2 costs are so variable too due to reserve, spot, and elasticity (depending on workload). It can be hard to compare.
> The workaround AWS support proposed was to reserve 2x capacity so we wouldn't run into this issue on subsequent deploys.

Thats pretty lame of them to make you pay them more money instead of functioning properly.
Actually original Hiren's boot CD was DOS-based.
I remember a couple of years ago trying the examples on and off. It wasn't until the beginning of this year that I dedicated time (few weeks) to it and started to grok what ZeroMQ was for me and how I could do blazing fast RPC with it. I created a RPC (async/sync) library for myself in Rust, Java and Javascript that uses ZMQ under the hood. While I don't plan to open source it anytime soon, I do recommend taking some time to dedicate to play around with it and try it in your own projects.
> it's always a hacked-together mess from an engineer who's likely no longer with the company.

Oh man, in 1996 I was at Nortel. Some Ms. C. in Computer Science (no longer with the company) left behind Perl cruft whose indentation levels didn't even match up:

whatever
{

}

type of thing. He didn't know how to operate a programmer's text editor.
Get to work at 9-10am. Work slowly doing trivial things. Eat long lunches. Go to the gym. Leave by 5pm. Get home by 6pm, and have the energy to get back on the computer.

Where as I have absolutely no desire to look at a computer when I GET to work, let alone after work.
Christ - what is with these Benjamin Button development fads? Dealing with the NoSQL silliness of the last few years was bad enough, but just wait until the next generation of devs discovers storing shit in flat files on the local filesystem...
Do you have an opinion on which to read first?
Timesheets turn out to be a very complicated product.

1. integration with accounting and payroll systems is mostly tragically difficult (and excruciatingly boring).

2. companies have wildly different needs for data entry and validation.

3. Unions in particular create fiendishly complex requirements for hours etc.

4. A captive audience means you can't drop "problem" users, and you do need to support outdated browsers and devices.

5. Timesheets need to be reviewed, revised, authorised. There needs to be a solution for when the manager is on holiday.

... And so on for another 20 items that are similarly complicated.

Timesheets are a great example of something that most people have used and think they understand (and I've seen software devs build a product for) but it turns out to be a far far harder problem than it appears.
Tip: since you're on magnesium, try magnesium glycinate if that's not already the kind you take. Glycine helps you sleep, especially if taken at night.
Long term, I'm not sure. But short term I think they have a very very nice future for themselves.

The biggest problem the Swiss have is that everywhere else seems really dirty in comparison.
Apparently Facebook does not like blogs/vlogs: https://www.youtube.com/watch?v=2pIJoPkh9IU
I personally feel the US taxes are generally progressive though not massively so, but significant exceptions exist. For example, the social security tax stops at $132,900 so there is a significant drop in marginal tax rates at that point.

Similarly, including or excluding donations, inheritance, and home sales from income can really change these numbers. I have seen analysis that says are system is progressive, regressive, and flat based on different definitions.

Honestly, that’s what I find most interesting about the system. The collision of a huge number of different interests result in a system that can be perceived mathematically different based on viewpoint. It’s like watching a magic trick in action.

PS: One of the most extreme divergent analysis focused on the sales and sin taxes paid by a group of homeless drunks. It varies by area but with 40+% percent alcohol taxes they where paying a rather shocking effective tax rate when you exclude benefits.
If this increases the supply of the tasty wild blueberries instead of those giant pieces of blue water in an organic sac, i’m All for it.
If anyone is interested in working with the language, AFAIK, DuckDuckGo's backend is primarily written in Perl.
> That's what programming is.

In my realm I need things to be supportable by lots of people. I use languages that are modern + people want to use, I document like crazy, I use opinionated frameworks that have good track records, I need to hire engineers that can support the code I/others write, etc etc. I don't find your comment to be true, and will even go as far to say I've worked with very clean legacy code.

Tangential: If you look at any "popularity of language" studies Perl has been on a downward spiral for over a decade. Ex: https://www.tiobe.com/tiobe-index/perl/

I see "well that's just x" as a poor argument for, well... anything.
Sure, I will email you.
We don't need Starlink or SpaceX or VPNs.

Radio is difficult if not impossible to block with clever operators. The system is known.

Satellite will always be subject to whoever is in power at the time and it won't work within a building.

If you want to get information in and out the best option is—and possible always will be–a network of skilled radio operators.
Did you forget about former Yugoslavia?

What about the Turks and the Greeks?

The UK might end up in a war in the next two decades or so if they slide any further.

War is a long term guarantee.
Given the lawsuit that is going between Elastic and AWS in the background, can someone confirm if shared rebalancing is a flaw in AWS offering?
Being misidentified as a criminal is a feature not a bug.