skysight-inc/HackerNews huggingface dataset:
It's somewhat disappointing that research is the primary motivator for the switch. PyTorch still has a ways to go in tooling for toy usage of models and deployment of models to production compared to TensorFlow (incidentally, GPT-2, the most public of OpenAI's released models, uses TensorFlow 1.X as a base). For AI newbies, I've seen people recommend PyTorch over TensorFlow just because "all the big players are using it," without listing the caveats.

The future of AI research will likely be interoperability between multiple frameworks to support both needs (e.g. HuggingFace Transformers which started as PyTorch-only but now also supports TF 2.X with relative feature parity).
Weekly Product Giveaways by Couponer
IANAL and this isn't the legal justification. But US corporations are treated with rights similar to actual people with slightly better treatment in some ways, slightly worse in others.

So: morally corporations should pay income tax because all persons are subject to income tax. And we have decided that corporations are persons. It's no more a "bonus" tax than it is a bonus tax when I pay my accountant and she also has to pay tax on that income (even though I have already paid tax on the money).
I think we'd just have to have a chat about the definition of what's excessive? Fining me $1m for something would be excessive, fining AT&T $1m for the same thing would be trivial. "excessive" is relative.

The GPDR is an example of what I mean; where fines are written as €x or y% of revenue, whichever is higher - which is intended precisely to make fines proportional. There's little sense levying the same dollar fine against Google and my local corner shop - a figure that Google wouldn't notice would destroy the other.
... and following this thread a little will bump into importance sampling, an interesting topic.
That's good, hopefully they keep a sign up or tell TSA agents as my spouse uses film regularly on trips and I'm sure not everyone will find out.

Just another headache traveling through the US I guess.
I'm not really seeing anything on his platform about not persecuting quality of life crimes. An entire page is devoted to his plan for policing car break ins, for example. I do see a section about drawing the court's attention away from misdemeanors so they can focus on felonies.
It's more that things were left undefined for portability and compiler authors (ab)used them for optimization enough for that to become de facto true (especially now that portability is easier).
2013 HN discussion: https://news.ycombinator.com/item?id=6538270
> I would do that job. I would take that money. I don't get a stupidly-inflated Valley salary with bonus RSUs, and I have bills to pay. I don't have a union that can protect me from nonsense. I know it's wrong. I would do it anyway, because I have been screwed by every company I have ever worked for, such that I learned that my ethics don't matter. Money matters.

You've identified a perverse incentive that requires punitive counter-incentive in response. Someone in your position will think twice about doing that job if by doing so, their freedom and ability to take care of their kids is put in jeopardy.

Of course, there needs to be punitive incentives at the top so that such that low-level employees are not pushed to act in ways that lead to results such as these.
If the patents were owned by a single individual instead of caltech, would the verdict be as large? They’d instantly be in the top 3000 richest people in the world.
You really need a road to every building for moving stuff to and from the building. Maybe one could put them all underground? Support the Boring company idea?
> No no no. That's not how probability works.

Pretty sure GP understands how probability works, maybe take a more charitable interpretation of their comment?
Well, there's only one Dave Chapelle, but millions of "Dave Chapelle"s that are still "broke".

So while you're not strictly wrong, I wouldn't consider it particularly positive distinction.
1. People enjoy the craft and experience of doing it. Why knit? Why paint on a canvas when you could do it in Photoshop? Why do people still buy records when Spotify etc exist?

2. Medium and large format film still look as good or better than digital 35mm, and are still affordable for hobbyists

3. The look of BW film can’t be replicated by current color digital cameras without an expensive (in time or money) modification to the sensor
Isn't that area part of the gang injunction no-go zone? That was federal involvement IIRC.
Missing a URL, but likely duplicate of https://news.ycombinator.com/item?id=22180559
What do those things have to do with each other?

Code can't use algorithms because it's written in PHP? I'm not following.
Obligatory mention that services are mostly an enabler for organizational scaling and, in my opinion, shouldn't generally be something considered for only technical reasons. Having hundreds of engineers working on a monolith is at least as challenging as having ten engineers working on ten separate services.

There is also a clear distinction, in my mind, between microservices philosophy and 'macroservices', as I call it. Buying into a system with more services running than engineers is very different than having a number of teams, each working on their own single or handful of services.

I would argue that the organizational scaling derived from microservices resembles diminishing returns somewhere in the domain between a single service (monolith) and more services than engineers (microservices).
I suspect we don't have those because it's politically unpopular. The disregard for traffic laws is so deeply ingrained and I also believe single occupancy vehicle is still the main mode of commute here. Also, the comments "what about the jaywalkers", "what about those pesky cyclists always blowing red lights", etc. come up ad nauseam.
I'm not in a place where I can watch the video right now, but are they doing this via like.. an LCD-equipped enlarger? This would be pretty cool. In the early 2000s I did a lot of experimentation with printing digital negatives to transparencies and printing them in a traditional darkroom or using alt processes.
Oh, you were. I just corrected myself after reading the article.
I'm a database guy, so the question I get from clients is, "We're thinking about breaking up our monolith into a bunch of microservices, and we want to use best-of-breed persistence layers for each microservice. Some data belongs in Postgres, some in DynamoDB, some in JSON files. Now, how do we do reporting?"

Analysts expect to be able to connect to one system, see their data, and write queries for it. They were never brought into the microservices strategy, and now they're stumped as to how they're supposed to quickly get data out to answer business questions or show customers stuff on a dashboard.

The only answers I've seen so far are either to build really complex/expensive reporting systems that pull data from every source in real time, or do extract/transform/load (ETL) processes like data warehouses do (in which the reporting data lags behind the source systems and doesn't have all the tables), or try to build real time replication to a central database - at which point, you're right back to a monolith.

Reporting on a bunch of different databases is a hard nut to crack.
I do it by riding slowly in front of them and pointing. Their options are to try to swerve left around me and get hit by a bus, jump the curb, or run me over.

I've not tried it in SF, this is me speaking of my experience in Houston.

In SF I'll block cars from making an illegal right by simply standing in front of them.
It's a trolling dogmatic paper. So of course some people will downvote you if you criticize the dogma.
As far as I understand, this is no longer possible on modern iOS versions at least, except if the app developers explicitly disable that validation.
Full-genome evolutionary analysis of 2019-nCoV
Or has all white crime been made legal in America?

Can you think of a time when it was significantly more likely for something like this to end up with execs in jail?
Sign Stealing Scandal
They do complement one another but docker has tooling that solves similar problems. Does docker-compose (https://docs.docker.com/compose/) fit your needs?
The deep insight is that we've built a system where people lack responsibility for their actions. It makes sense to do harmful things that are appear good in the short term because there's no accountability.
Maybe the title should be “Bad Engineering is the Future”.
Have you been in a French city of late? I almost couldn't visit Tours-centre because of all the diesel smell a few years ago.

It has improved slightly in the last 2 years but it will take a full adoption of EVs (and increased public transit) to resolve. It's not like France is lacking for fuel taxes or road taxes and insurance costs. Demand is still too high.
The author does not seem to understand when to correctly apply microservices. There are two basic use cases: 1) Different parts of your solution have different load patterns and it is economically beneficial to scale them at different rates and 2) Different teams need to be able to work & ship autonomously. It's not at all about technical merits or architectural beauty. It's about people and costs.
This. I'll even supply an actual illustration:
https://humantransit.org/2012/09/the-photo-that-explains-alm...
My experience with microservices has been just a shift in worries. I don't worry about scale or ssh configs but I rather worry about cloudformation and cloudwatch or billing impact. It has also been some challenge to get testing locally to work easily and there have been quite a lot of meetings and discussions used up on that alone. I don't find the microservice pitch from a developer perspective to be easier at all, actually harder overall. I do like the approach of gcloud or elastic bean stalk better for cloud as you have an auto-scale but still can do local testing easily for a monolith approach. The use case for microservices IMO is more like you have a couple of highly-used sets of functionality that are disproportionate to your monolith and can be split out to save money but not to build everything around microservices and pretend everything is easier. Personally I feel my cognitive load increases when using microservices purely.
I have never worked on a real 'production' monolith. I wonder what i'm missing out on :)
LA county sheriff to publish all legally allowable content online
Isn't domain information still in the clear? (What specific domain you're connecting to.)
Explainer: Why the New Coronavirus Is So Dangerous
For reference, 300-350mrem is a decent estimate of your annual dose of radiation. If you fly a lot, smoke, or live in areas where the ground releases significant amounts of radon, your own annual dose can be twice that.
Have you looked into Zig (https://ziglang.org/)? It's a little more than what you've asked since it does support compile time generics. But is specifically targeted at removing undefined behavior and improving safety.
There are lots of fun ways to smooth out short-term variation in game randomness. This article shows a few used by various Tetris games, with one of them being your deck-of-cards approach: https://simon.lc/the-history-of-tetris-randomizers

One of my favourite techniques not listed there is weighting the probabilities by distance, so individual outcomes get more likely the longer you've not seen them (making the gamblers' fallacy real, I guess).
For when ordinary YAML isn't quite crazy enough.

Worth reading this if you are considering using it: https://www.arp242.net/yaml-config.html
My current impression is that Gmail is sort of broken in general. There isn't really anything you can do to insure that an email will get delivered to Gmail with 100% certainty.

Presumably people who actually care would not be on a free email service in the first place...
I would prefer if such evidence had been included in the initial post to make for a full argument.
This is a surprisingly unintelligent move from OpenAI. It adds corporate inertia to something as mundane as choice of DL framework.

Imagine you worked at OpenAI. Imagine you wanted to experiment with Jax, and that it turned out to be the best solution for the problem. Now you can't ship without a solid technical justification.

Except, it's not really a technical justification that you need. You need corporate clout. You can't just be a junior engineer and make a decision that goes against corporate policy. That's the point of having a corporate policy.

I can hear a thousand people about to type "C'mon, OpenAI isn't a normal corporation." But it is. Every corporation is a normal corporation. And having policies against specific tech should make productive programmers pause.

People get jobs at companies based on whether they use React or Vue, for example. And in DL, a programming library is basically a programming language, so it's one step more powerful than that.

Here's an example. Pytorch, as far as I can tell, doesn't support running code on a TPU's CPU. (I could be wrong about this!) When you enumerate the list of accelerators available after connecting to a TPU, you get a list of 8 entries. That means they only support executing code on the cores of a TPU, not the TPU's CPU. This is a huge difference. It means you're restricted to 8GB on TPUv2-8's (which you get on Colab) instead of 300GB.

Does that count as a solid technical justification to use Tensorflow for a research project instead of Pytorch? Who knows. But who wants to be the odd one out on corporate politics? Especially if a project doesn't generate any tangible results, which is often the case for research.
Realtime charts, this is cool stuff!
Love Island Hashtag Analysis
>> "Java sucks" is so 10 years ago.

I mostly agree, but I also work with enterprise software products that have legacy code bases with baggage that is over 10 years old, so there is still a lot of Java software that sucks. We're talking about applications that take minutes to just load and display a window on otherwise fast hardware. And in some cases, the entire purpose of the application is to basically slap a GUI around an XML configuration file.
I have seen monoliths successfully transition parts of their functionality into small services. I have not seen a microservice-first approach work very well. When you're building something new, your intuitions about which parts are going to be tightly coupled and which parts are going to be relatively independent are just guesswork.

Once you've iterated on a monolith enough to see which parts are relatively independent and would actually benefit from decoupling, then you can move them into separate services.

One example that comes to mind: I wrote a recommendation service that also handled user feedback events. This was the easiest way to start. After about a year I saw that we were iterating faster on the event processing than on the actual rec delivery. We were also deploying this monolith across more machines mostly to scale up event handling capacity. So we broke the high volume event handling out into a separate service that was smaller and optimized exclusively for event processing.
I agree with your words but the realist in me has to point out that microservices don't force you to do anything, it's a pattern not a highly opinionated and restrictive framework.

There are plenty of clusterfuck hybrids out there with services sharing database state etc. Anything can be an antipattern when you add people into the mix.
The article touched on it and I've experienced the same thing... The added complexity of having to manage 10's to 100's of different code bases, pipelines and deployment concerns is a huge downside and should be considered before adopting the new shiny.
Announcing the Third Workshop and Challenge on Learned Image Compression
If I read it well, this grant is personal income though.

If the company has to pay 2-5k in monthly taxes, that will be on its revenue. If you have no revenue yet, then I don't imagine you will have to pay that much in taxes
There are a lot of unacknowledged tradeoffs in tools like Haskell. For example the value of Haskell is balanced against ecosystem value of having 10M people using the same tools. Getting 10M people to choose Haskell is actually a goto market strategy problem that could be solved by a charismatic leader, but I don't hear anybody from that community talking about that.
Apple delivers a new redesigned Maps for users in the United States
> Optimize your existence as you see fit with that information!

That sounds very intriguing, yet I don't really have an aha!-moment. Care to give an example or two from your personal experience?
In the venn diagram of "new startups or ventures", "Existing IT shops that are already heavily invested in infrastructure", and "every business", the first two do not cover even close to the entire area of the third.
Or management, those Snidely Whiplash types who create unethical requirements for innocent programmers to implement.
> In general, anything that was added to a language to support generics or to hide pointers and memory management from the developers on a language that isn't a lisp has only produced more harm than good.

I understand why you would want explicit memory management, but what specifically is harmful about generics?
Good question, I don't think they talk about the b&w digital prints in the video afraid. https://www.harmanlab.com/ is the website for that, which I'm just looking at, but can't see the machine they use at the moment.

It looks like they may use https://en.wikipedia.org/wiki/LightJet for the bigger prints

They seem to use a specific type of paper for the machine too - https://www.harmantechnology.com/amfile/file/download/file/1...
My account is still grandfathered in with 30k free per month.
PHP is a very good choice. If you want to refresh your knowledge of PHP take a look here: https://phptherightway.com/

It's fast. PHP has great documentation. PHP ecosystem is now based around Composer, in comparison to mess of package management in JavaScript and Python, Composer is just wonderful to use. Packagist has ton of libraries. Share nothing architecture is very easy to maintain and scale. You can do strict typing. There are static code analysis libraries like Psalm and PHPStan if you want features normally offered by compilers. It's easy to hire devs. There are two wonderful frameworks that moder PHP is centered around: Laravel and Symfony. There is also community body issuing standards to ease framework interoperability: https://www.php-fig.org/psr/

The app seems to be written in Laravel, so you can take a look here if it's your coup of tea: https://laravel.com/

Having said that, Wordpress and other old code bases are still a mess. But stable mess, and business like stable :) .
[I'm speaking only from the US perspective]

The only difference is if you own the gear or not. If you do own it, then it is CAPEX, and the gear goes on the balance sheet and you can only depreciate it according to the schedules ( in some cases immediately 100% but most of companies blow through that number really quickly ).

In all other cases it is OPEX.

The rule of thumb is that all OPEX can be used to offset the revenue, which is god sent to most companies that aren't printing gobs of money.

So if you make some money and you are past 100% deduction thresholds, when owning gear beefs up the balance sheets and at best slightly decreases taxes while spending money on OPEX significantly decreases taxes.
I agree that for most startups, monoliths are all you need. But at some point, as your engineering organisation keeps growing in size, there are other benefits to microservices. Benefits not addressed in the article.

Data isolation. Allow individual teams/services to own their own data stores, and prevent any other team/package/service from reading or writing to their data store, and inadvertently breaking the associated invariants.

Performance isolation. Prevent one team/feature hogging too much memory/cpu/io, and negatively impacting every other team as well. Debugging performance hogs in a sufficiently large monolith becomes infeasible at a certain point.

Deployment isolation. Allow individual teams to made code updates and deployments whenever they want, without having to be tied down by a company-wide deployment process.

Language/dependency isolation. Allow different teams to use whatever language, dependencies, and dependency versions make most sense, for their use case.

At bigger companies that have hundreds or thousands of engineers, monoliths simply do not scale, and need to be broken down into more manageable pieces. It's unfortunate that smaller companies start cargo-culting these same practices without thinking critically about whether they actually need them.
I think this is a more modern alternative to Sendy (https://sendy.co/) which is a little cheaper. (no affiliation except being a user)

Sendy does look like it has more features though - and it has been around for far longer, corner cases debugged and all. I’d love to hear how this is any different from Sendy.
AI NEXTCon Seattle 2020
You had a point about error checking that I think is pertinent to my not being in Ansible's niche. If a service fails to start on a single host, it's because I'm already tinkering with that configuration and hence will notice the failure. Whereas with tens of highly similar hosts, you want to find out about exceptions sooner. I'm actually getting to this point with some common things (apt upgrade), hence looking into Ansible again recently.

Overall my goal is to write very few on-host configuration scripts, and prefer overwriting files. For example, most triggers are simply service restarts, which can also be performed by a full reboot.
Don't SSD have some kind of cyclic redundancy check?
For large, repetitive configurations (Kubernetes configs, CloudFormation templates, CI job configurations, etc) you often want ways to abstract and/or DRY your configurations. Kubernetes folks use mustache/jinja/Go templates via Helm, which is a real mess. CloudFormation builds its own (shitty) evaluation language on top of YAML. This presumably aims to improve on those sort of hacky solutions. I feel strongly that the "right" solution is either (1) generate a YAML config with Python/JS/etc or (2) use a terminating expression language (I think that may be what this is). Since (2) implies a much steeper learning curve for average developers, I opt for (1).
Those responsible for the termination decision include the two subjects of Smith’s complaint, Secretary General Fang Liu and Council President Olumuyiwa Benard Aliu

Of course, we've no idea of other personal and political dynamics between the complaint subjects and the whistleblower, but at least on this summary, something stinks.
The phrase that comes out when someone proposes NoSQL is "we're not Google / Facebook."

Most applications don't need to run at "Google scale," thus they don't need the expense of relaxing ACID.
There are a lot of places where specific turns are prohibited, but I don't think I've ever seen a street that was entirely blocked to cars based on the time of day.
> Reporting on a bunch of different databases is a hard nut to crack.

It's not necessarily a bad idea though :-/
So I know someone who is very much into photography but is of modest means. Turns out you can pick up a second hand analog camera and film for it for very little money, and achieve quality that you'd need something like a Canon EOS 5D for otherwise. Obviously there are things you can't do with the analog that you can with the 5D, but not everyone is made out of money.
>HSTS has a certificate pinning extension

You mean HPKP? AFAIK it isn't an extension, but rather another feature. Also, it's deprecated at this point.
One reason is that the services are actually quite cheap if you are running a real business. Likely better to spend time on your core thing instead of tinkering with mail server.
Wokeademia