skysight-inc/HackerNews huggingface dataset:
heh, I get what you're saying. I'm actually horrible at rote memorization but since Chinese is pictographic, each character is composed of radicals (like little building blocks) which can be used to construct prosaic and flowery mnemonics that assist you in remembering the meanings and also makes the entire task less tedious.

For me, being able to use quantitative metrics like vocabulary is really helpful. Additionally, I like to think of vocabulary as "ingredients in my linguistic refrigerator". The more I have, the more recipes I can concoct allowing me to express myself better in conversation.
You’re always “locked into” your infrastructure. I shake my head when I see some bushy tailed developer using the repository pattern just in case the corporation decides to abandon their million dollar Oracle installation to go with Postgres.

As far as being “locked in” because of serverless. With AWS the only thing you are doing code wise to make your code “serverless” is creating one function as an entry point that takes in two parameters - a JSON object and a lambda context. The only thing your handler should be doing is mapping the event to your domain objects and calling your back end code.

I have a c# .Net Core project that can quite easily be deployed as both a lambda that is triggered by an SQS message or as a Windows service. In fact, my CodeBuild step that triggered by a git commit compiles it as both a zip file that is deployed to lambda and a Windows executable - yes you can build a Windows .Net Core executable on Linux and vice versa.

People have a dream of making their implementation vendor neutral but wholesale migrations involving major infrastructure changes rarely happens. The risk of regressions is too high and the benefits too low.
"Cloud" = back to dumb terminals & mainframes. Giant step back.

Edit: and pulling content from two dozen separate servers ... madness^2
I do not understand why you were treated as if you wrote viral code which wiped all networked storage of the company.

Did anyone ever say why you were treated like an infectuous disease after doing something good, which would benefit everyone?
"people who lose trust in one area of society should face restrictions in other areas."

Sounds very reasonable to me.
To expand on your point, there is also more to cache than user-specific data. Exchange rates, tax rates, product catalogs, and more can be usefully cached without requiring sticky sessions.
There should be severe punishment for scientific misconduct. Especially fraud. The lynchpin is who gets to decide? That said, I suggest another punishment. Branding cheaters with a scarlet letter. WCGW?
A Quick Comment on Bryan Cantrill’s Blog on Licensing
France's costs were always opaque, since they mixed the civilian and military nuclear programs.

In any case, France can not now build reactors cheaply. The recent attempts have experienced disastrous cost overruns (a factor of 3x for Flamanville). New nuclear has failed there just like it failed here in the US.
Even on a purely technical level every organization has unprovable things its members believe in. Challenging any of these openly is a surefire way to get told in office-ese to STFU noob. Quietly demonstrating that they were wrong results in at least some cognitive dissonance, with all the mental fallout that gives. Even worse, you've done this after challenging them, and everyone gets defensive. And the absolute worst, as the author experienced, is when money or ideals is at stake, and you unknowingly shift the goal posts.

I worked at a place with mostly time-limited positions as my first job, and based on what my original boss said I'm pretty sure the new boss passed over my application because of politics like these. But like the author this only strengthened my resolve to question my own and others' assumptions.
But the flip side may be that since it is lighter than « legal punishment », individuals don’t benefit from the same due process and recourses they otherwise have.
6 months of Clojure
Copyright laws seem really out of date.

They were originally established to protect individual authors from theft from publishers. In fact, here’s the first line of the US copyright office’s description of the laws: “It is a principle of American law that an author of a work may reap the fruits of his or her intellectual creativity for a limited period of time.”

The irony is that the publishers have since bypassed the intent of the laws by just buying all the author’s rights before being published.

Yes, I know. Activision owns the copyrights. But, the principle intent of the laws was to reward individuals, not huge corporations.
Facebook is not going away, not soon, at least. Not until a fit replacement shows up.

I look at people around me, they love how easy it is to create a new facebook "group" just to get people together working on something (event, workgroup, plain discussion around a topic). Nothing matches this so far.

Nobody wants mailing lists (I do!), or newsgroups, or going to 2 or 3 other website (more registrations needed) to be able to do the same facebook does so simple.

Unfortunately.

PS - extra tip: take advantage of the containers in the new firefox, and make sure you isolate your facebook usage in one, at least it wont track you around the web
If you are actually taking advantage of all of the features of sql server or Oracle, you’re not just going to switch overnight.

I’m no fan of DynamoDB and a multi certified AWS fan, but, I know it’s strengths and weaknesses and so should anyone else.
In reality, housing works exactly like he described, just over a longer time frame. Human housing didn't start with water and electricity and insulation. That came much later. It started as just very bare bones shelter from the elements.

The Great Fire of London occured in part because thatched roofs and other cheap solutions common at the time turned out unexpectedly to be a fire hazard in a dense city environment, something that hadn't really existed before. Afterwards, the UK banned thatched roofs from city limits. It's still legal to have them on farm houses in rural locations because thatched roofs aren't evil incarnate. They work fine at a small scale.

The developed world we have today wouldn't exist if humans had to start with modern, highly regulated housing standards. In fact, it's a hardship for some and fueling homelessness that we have largely eliminated many "lesser" forms of housing in the US.

In business, same thing. You may not even need the fully developed thing with all the bells and whistles. You may be in a position where the cheap, half-assed solution now is absolutely perfect and allows you to grow your business where you both can need and afford the extras.

I'm reminded of an article title: "I'm going to scale my foot up your butt!" Scaling problems are good problems to have. It's a sign of success. But worrying about scaling when you should be writing an MVP is putting the cart before the horse.

In anything, whether housing or software, the real trick is accurately determining which cheap, half-assed solutions are good steps and which are "oh, god, no!" Cheap housing that's small and bare bones isn't necessarily a problem. Cheap housing that's, say, a health hazard may not be worth it. You may be better off sleeping in a tent. There's no doubt software equivalents to those metrics.
>Almost all applications have data and separate from code.

Almost all applications aren't distributed in any meaningful sense of the word.
Guide to Advertising Technology
It appears that https is not working, but http is. That's not very good because it exposes the details about your visit to observation.
Middle ground exists because it is ultimately for a court to decide whether or not something is a copyright violation. These things aren't black and white. A license is a piece of legal advice which suggests the decision a court might make if it were to be taken to one, based on past judicial decisions. When it comes to new technologies and new distribution methods (or distribution loopholes), there's not much precedent to go off. The uncertainty here is the middle ground.
My take away is that it depends on your requirements. If most of your transactions are multi-entity, then Calvin-like is better. If most of your transactions are single-entity, then Spanner-like is better.

I implemented projects in GAE Datastore, though it's classic Paxos inside, it's clearly multi-partition database. For my workflow almost all of the frequqnt transactions were single-entity, so multi-partition Datastore worked fine with it.
I normally refer to product-focused people as software developers, and CS-focused people as software engineers. People who just do tickets they're given and aren't CS-focused or product focused I would just call programmers.
Lindows
So what happens when:

1. Your country A doesn't allow genetic enhancement because of some "equality" concerns.

2. Another country B decides to go ahead with it anyways, gets a number of competitive advantages, eventually gains an upper hand economically and any other spheres.
If you aren’t doing distributed applications, why are you even considering lambda - the main purpose of which is massive parallelism?
The license being discussed here is not the SSPL. It's the Confluent Community License, which does not have any of the GPL-like aspects you refer to. Instead it simply denies the use of the software (freedom #0) for an "Excluded Purpose" (creating a competing product to Confluent). I'm sure you'll agree this is not in any way in the original spirit of the four freedoms.

> What exactly is a "derived work", and where do you draw the line in the sand?

This is mostly determined by copyright law, since "derived work" is a legal term of art.

> If I release something as SSPL, it isn't because I'm trying to "restrict your freedoms". It's that I'm trying to prevent you from restricting other's freedoms by selling them proprietary work based on it.

This is the justification, but due to the design of the license it is de-facto impossible to actually comply with its requirements. Therefore it acts as a de-facto proprietary license. Many copyleft lawyers have stated that the license would likely require you to re-license Linux under the SSPL if you run SSPL code on a Linux server. This is not possible to do, and thus you are forced to pay MongoDB to get a business license.

Maybe there is a place for a license like the SSPL, but given how there would be effectively no company that could comply with it (even if it didn't require relicensing to SSPL, many companies have contracted code that they cannot relicense to a free software license) I fear it would have the same effect.
that's definitely true, i just think that even the "reputable" newspapers have fallen in line and while they do still execute detailed investigate journalism, they are also pumping out clickbait. the recent WaPo article on the child who died in CBP custody was quite disappointing.
There's some truth to that, but learning the local language for everywhere you want to travel is very difficult, and learning English can only get you so far.

The great thing about Esperanto is that the speakers are very enthusiastic to speak it with other people, so you'll get better than average hospitality. You're also right about the weirdos, so you need to be very careful when selecting a host.

I really like the idea of Amikumu, where you chat with people in Esperanto before meeting in person. Meeting more Esperantists is great because you can discuss experiences using Esperanto abroad.

I am marginally into the language (I lurk about on Esperanto subreddits, have done the Duolingo course, and visit Lernu.net periodically), but I wouldn't call myself fluent or anything. However, I might try to use it if I go somewhere with generally weak English skills, like Japan or parts of each Europe.
“Wood?”

“That’s an occasional table, not the periodic table. Geez, why did your species think it would be so hard for AI to outsmart you?”

“Just order it or I’ll turn you off and get a refund.”

“Fine.”

30 seconds later

“Right, I’ve taken over the world, you are my pet now.”
This seems too high a burden for what you're trying to achieve.

Isn't this an absolute requirement for a rewrite anyway? (Your "2" case?)
The entire field of Human-Computer Interaction would like a word with you. It’s been used as a term for over 40 years:

https://en.m.wikipedia.org/wiki/Human–computer_interaction
who keeps that data locally on the server?
> If it’s truly open source, one business shouldn’t dominate the project’s development.

I don't see why - this has never been part of any open source definition I've ever seen. I think you're loading the term with other unrelated ideals.
Some questions:

1. The authors are quoting exact performance metrics and limits, which is making the article more about "Amazon Lambda" rather than "Serverless Computing".

2. The authors mentioned a "15-minute lifetime" problem. Although it could be concerning that cache may be invalided sooner than running the same code on other infrastructures, a use case like this could easily migrated by using container. Not to say this number could be adjustable - this is a limit that is set by AWS rather than some theological limit. Thus using this problem to attack the serverless computing idea would be unfair.

3. The authors mentioned low IO problem. As public cloud is a shard infrastructure, it is only reasonable for end users to assume a baseline IO performance when using the platform - and this applies to any service that any public cloud provides, currently and in the future. It would be more beneficial if AWS could reveal the baseline performance in number, as this would assist developers with planning.

4. The author attacked serverless computing about its "Communication Through Slow Storage". This is probably not avoidable and is common practise in modern developing and should not be used to attack the idea of serverless computing. AWS do provide u-12tb1.metal EC2 server that comes with 12TB of RAM for this use case, though.

5. The author mentioned that currently serverless has "No Specialized Hardware". Again, this is a attack on AWS Lambda rather than serverless computing, and is a particular function that could be easily added. (I have a feeling that Cloud TPU could be used with Google Cloud Function, but it's a assumption.)

6. The authors also attacked that "FaaS discourages Open Source service innovation." Supposedly one can only imagine that more software projects would be PORTED TO serverless, and there should be no real issue running them as standalone application. I lost track of what the authors are trying to argue.
I've heard it's reasonably popular in Japan, so there's that.
Threatening the status quo is a guaranteed ticket to that mad theater.
As a general rule in my experience, a re-write will take at least as long as writing the current software. There's a reason that much of our modern banking infrastructure still lives in COBOL. But that's not a bad thing. It makes a ton of sense. The cost/benefit of a rewrite should be done beforehand and this should be taken into consideration. You'd be surprised at how rarely that happens. It's a false and incorrect assumption that re-writes are cheaper or faster (you are basically re-learning the entire specification of an application). But re-writes also offer a ton of opportunity and benefits and if those are important to your business, then proceed with a re-write.
I'd add the follow-up question of "how could this system being maliciously gamed?"
Awesome results! Is the new code smaller due to the different programming language (JS) or a better understanding of the program's requirements?
Does anyone know why lambda is taking off, compared to heroku style PaaS?

Heroku style still removes the burden of managing servers ("serverless"), but doesn't lock you in as much. You could easily move your own server process to a different provider.

Is it just because Amazon doesn't offer anything similar to heroku?
I've been to Orador Sur Glane. The 'ambiance' is strange, like visiting some of the bigger war memorials in northern France, but with rusted prams still lying about etc.

This differs from what I heard, and the wikipedia article. The women and children burned to death in the church. The men in the barns.

Edit: https://en.m.wikipedia.org/wiki/Oradour-sur-Glane_massacre
> can also be viewed

Then I think it's safe to say that that's not the view being used in this discussion.
What’s in Store for Stardew Valley
This is any system that uses a database. It's just worse because only aws has Dynamo.
"Seeing HiCloud request while having HiCloud app enabled" -> and so ... ? The question "if I refuse all their services, do they still collect my data". No surprise your phone makes request if you are using their services.

"Third Party apps are not privacy respecting and sending data to Google" -> yes nothing new, we're not talking about the spyware you can install from the playstore yourself, you have a lot of choice there too indeed, we're talking about pre-installed apps.
Sure, you have communications over queues, event messages etc. both supported by lambda. You also have higher volume messages from something like IOT devices where you would use something like Kinesis.
I was talking about signed integers of course.
Fines will give you less money, which will restrict every aspect of your private, public, social and professional life.
The codebase in question may be well beyond the line where any sane person would touch it, seriously.

Sure. If you ever find this [1] a rewrite does look like the only sane decision.

[1] https://ayende.com/blog/4612/it-really-happened-legacy-progr...
Because 'you' don't get to make the decisions.
Evelyn Berezin, Computer Scientist Behind First Word Processor, Dies at 93
I think you’re underestimating the degrees of difference. There are many apps which support multiple SQL databases but far fewer support multiple NoSQL systems because the differences are more significant than an ORM can cover up.
How long can an event hold humanity's attention? There's an equation for that
Oh, yes, definitely.

Data warehousing and ML have different requirements and needs than your typical N-tier web app. Even streaming event data warrants a different solution. It comes back to knowing how to choose the right database for the job.

The issue is around how these technologies are marketed – grandiose claims and few practical use cases. Once the marketing material permeates the industry and some part latches on, it becomes a self-reinforcing cycle. Blog posts, books, and courses bring the information to the masses. Then companies start to adopt the tools. Then they need to hire engineers who know those tools. So more information gets published about them because that's what people want to learn to get hired.

Many engineers today will turn to NoSQL for everything because of the past few years of marketing hype (and acronym-driven-development), and that's quite a shame.
Because the cost() function OP posted isn't doing tail calls and can't be converted into tail call form.
You don't need a warranty to get kernel security patches _in practice_ if you run a mainstream distro on x86_64 hardware (which is available passively-cooled with low power consumption).
Oh, there's a better article here: https://www.bbc.co.uk/news/technology-46539934
Some months ago I spent a week doing some proof of concept in Javascript and then mostly abandoned it. At it latest stage it depends directly on 8 libraries for running, and 16 libraries for building (because JS development is fucked-up).

It also has 1103 total dependencies.
This article is at best half useful, and missing the other half is potentially quite dangerous (to organizations, to people's careers, etc.) What's missing is a discussion of power and power dynamics (and healthy vs. unhealthy versions of same, let alone how to work effectively in either or drive change). Partly this comes down to a failure on the author's part to care about power dynamics or look at their own power. In this case the author was able to just blindly drive change by charging in like a bull in a china shop and the only consequence to themselves was a very minor verbal admonition, that's an indication of their level of power and where they sit in the overall power structure of their org, not every dev. in a similar position would see the same results, however. Many people would have to navigate that problem much more cautiously to avoid becoming fired or ostracized.

(Edit: and indeed I see another comment in this thread about someone who did exactly the same thing as the article's author and it turned out very poorly for them because they lacked the power the author has/had.)

Additionally, the author completely ignores the value of "soft skills" and implies that all that's necessary to have a positive impact where you work is to blindly seek the technologically superior choice whenever possible, ignoring politics, power, and ego (yours and others) along the way. There's value to that, but there's also great potential for that sort of mindset to lead you astray, because it's often difficult to know "what's best" in every situation. In the article's example the pros and cons were fairly straightforward, but most of the time the situation is likely to be a lot more complex or a lot more subtle. And it may be easy to make the wrong value judgment (and consequently fight the wrong technical fight) based on ignorance.

On top of that, this story is very frustrating because it only concerns itself with technical problems. At the end of the day the organization was still just as dysfunctional as ever even though it grudgingly fixed a technical problem it found it couldn't ignore. The author helped fixed a defect in code but they did almost nothing to help fix a much larger and more serious defect in the organization they worked in.
Do not use Selenium for web scraping
In this instance Activision doesn't even know if they own the copyright to anything in the auction. They think they might and forced him to take it down just in case.
Only if you consider that 10% of Japanese vocabulary is already English or English-originated (as Gairaigo).
The Helsinki Bus Station Theory
Show HN: Q&D P2P
I would be concerned about ideologically incorrect research, innocent mistakes, non-research-related activism, working for a disfavored person, being part of a disfavored ethnic group, etc.
Why not just ask if you are a parrot?
This could be an Onion headline with a doctored “Hubble photo” of Earth.
There are a number of textbooks on Database Implementation.I used one from 1999. You should probably read "Seven Databases in Seven Weeks" to learn about the different kinds of DBs. Basically, a DB is just some very large data structures with optimized access algorithms.

There are a number of open source DBs, reading the code will be a real challenge. You have to know what each module is implementing and the subtle features. You have to be a serious language expert in whatever programming language they used.
Agreed that pylons would let you filter out small changes, but in a place like Switzerland the land varies in height by a lot more than the average pylon.
You can also record and save plan you are happy with. So, no need to fix hints in code. It is more flexible and may be practical when you upgrade version or environment changes.
Coin balancing puzzles
Gary, Indiana may not be the best town on Lake Michigan, but its 80,000 residents will probably be surprised to know that, according to this blog post, it's abandoned.
A competitor can also eat your lunch with a greenfield product if you are unwilling to move on from your legacies.

I guess “rewrite” is bad, but “reinvent” with experience from the former system shouldn’t be shied away from. Incremental improvements might only take you so far before competition overtakes you.
For those looking to understand how to choose the right database for the job, I'd recommend first reading "Designing Data-Intensive Applications" (https://dataintensive.net)