skysight-inc/HackerNews huggingface dataset:
From the article:

They acknowledge that more research will need to be done to prove that the marks were made by whales—but if their suspicions turn out to be correct, it could impact licensing for mining in such areas.
I love living and working in Japan, but I wouldn't recommend moving here unless you're committed to becoming fluent in Japanese and integrating into the culture. This is probably mostly true for any country one could move, but Japanese is one, if not the hardest language to learn for native English speakers.

I do, however, recommend everyone visit! Japan is a beautiful country with a unique culture and has something for everyone. You'll be safe, and have all the amenities you would expect from a first world country.
The plural of anecdote is not data. And Korean people have been oppressed in the past, and no attempt to rectify the situation has been made by the government. That's why a lot of Korean people born in Japan gravitate towards less savoury activities.

Plus, Japanese took Chinese and Korean women and forced them to become whores or "comfort women" for the Japanese soldiers stationed in the mainland. As recently as 2014 the Prime Minister of Japan said there was no evidence that the Japanese government took "slaves".

And the second point, which you don't touch upon, is if you look even vaguely Japanese at all, you are expected to follow all the social norms. If you don't, they give you a pass.
On the German _Autobahn_ there is no general speed limit.

There is a speed limit of 50km/h in towns and villages, which is often dropped down to 30 in pedestrian rich areas, in front of schools and so on.
There is a 100km/h speed limit on normal roads outside of settlements. These are one-lane in each direction with not separation.

On the Autobahn, you have at least two lanes in each direction with separation. There is no general speed limit but there are many speed limited stretches, usually to 120km/h. These limits are on about 50% of the Autobahn.

Fines for speeding are not really high, but you do get "point", so multiple violations can lead to losing your drivers license.

To get a license, you take a minimum of 12 driving lessons and a theoretical course. There is theoretical test and a practical test.

I think the high-quality drivers education + the safety features of cars + the mandatory inspections of the cars (yearly) help offset the safety risk of the higher speeds.
Give us the data already:
https://en.wikipedia.org/wiki/Life_expectancy
> Since some similar exploits have been discovered for AMD and ARM CPUs, the answer is probably “no”. But certainly customers are upset.

Whats to be upset? Don't update if you are upset. Choose between perf/security. What are the options, anyway? You can be upset that the things are the way they are, however you can't blame Intel/AMD/ARM, etc. You should have been upset if these vulerabilities were known and not fixed thou.
It will mostly be developers taking over their jobs and sysadmins being replaceable getting more pronounced.

In fact in most companies this is always the case. They routinely lay off sysadmins, qa and other support personnel and ask developers to take over.

I'm now seeing trends of tech leads sort of roles doing the same jobs as a managers.

If your job involves some prime mover to which you are just a helper/enabler, its likely you can be easily eliminated.
Yay, you misled users and stole content! Seems like you are actually proud of this. I gather you realize this and did this in the best “white hat” spirit, although that’s not really what I get from your blog.
The only problem with Intel is the price point. Given that the R&D is sunk, and the COGs are about 8x, their profitability is entirely market demand.
Hybrid Cloud Hosting: Cloud Web Hosting Solution for Modern Businesses
Since Cloud Computing services inception, cloud services have enticed many organizations and even those reluctant to embrace the technology. We are at a stage where the market demands the next, upgraded version of cloud hosting services, while on the other hand, we still have a bunch of them, standing miles away from cloud solutions because they doubt its security features. For best Cloud Computing Services check our Unisecure Data Centers website : www.unisecure.com
My guess is Intel will revert the license change soon. It's just too absurd to stay. But if not, I wonder if distros could have two packages, named with appropriate and well-deserved passive-aggressiveness, e.g.: intel-microcode-insecure and intel-microcode-legally-restricted.
Condensed matter theorists usually don't look for a job that measures them on the quality of their research code.
Well, first get everything under source control, if it isn't already. Get the build process organized so anyone can do it.

Start adding comments without changing code. Any time you touch anything, comment that area as you figure it out.

If you find unused code, put something like #ifdef OBSOLETE around it, rather than removing it immediately, and stick in "assert(false)" where something is unreachable.
I think you mean domain, not tld.

Tld is the last part of the domain, the .com, .eu, .in, ...
Missing context here being that this specific allegation was made, within the past few months, by a British foreign service official who was posted to Beijing at the time.
You sound like a novice programmer.

If it works, don't fix it.
They also got rid of their CEO this year.
When they get to 220C they are going to fail pretty quick.

At those kinds of temperatures, oxidation is much faster, and you'll get heating and cooling stresses causing micro fractures as the load on the line goes up and down.

As the resistance increases even a little, the temperature will increase more, making the above effects even worse.
Windows automatic updates are one of the easier ways to get the new microcode without agreeing to the new license terms. But there are plenty of other reasons to disable Windows Update (not that Windows will respect your decision).
I'm not aware of any good opportunities out there - did you start your own thing or work remotely?
Here is one thing we can do about it: make public service announcement to our users that we no longer recommend Intel CPUs because of security holes, censorship and crippled performance.

I am going to do that today. While we only have several thousand users they do CPU intensive work, buy a lot of new CPUs and rent a lot of servers. My small contribution will likely amount to low-mid 6 figures out of Intel pocket in coming 2-3 years.

Please consider such announcement if you could do some damage as well.
Weather
Weather forecast site: http://sat24.cc
Has anything even remotely similar to this ever been enforced anywhere? (Apart from the US)?

Once I have the application (or in this case, the microcode) it would seem the data I produce with it is mine to do as I please with? Otherwise it would be like microsoft saying that I couldn't publish any .docx files online that I produced with their software?
Let us not generalise and make racially charged accusations against another culture please. If it personal experience you had faced it could be anecdotal.
They didn't down rank it, they delisted it just like they would delist child porn or copyright material after receiving a dmca notice
How a Facebook army became a lifesaver for Kerala during the floods
NASA administrator sees lunar water as key to returning to moon
Can I ask you a few questions, if you don’t mind. Are you fluent in Japanese? Have there been any major instances of discrimination at work? I know you’ve been there 10 years, but is this a place you’d be happy for the rest of your life to start a family and potentially retire?

Please ignore if any of these are too uncomfortable or invasive.
Is Chrome the only browser this trick worked on?
Stay or go. That is your first decision.

If you stay:
After 3 months you should have a good feel for the project. After 6 months you should be able to regularly make small contributions.

After 9 months:
Spend 10% of your time documenting the problems you see and the changes that might solve those problems.
Spend 10% of your time planning another work project that is unrelated to the main project.
Spend 20% of your time honing a skill you want to learn.
Spend the remaining 60% doing the work you were hired for.

After a year, if you feel the same way, discuss with mgmt + senior the problems you’ve been documenting and if the changes you suggest are something that should be implemented.

Iterate.
People are upset because Intel is not allowing people to run benchmarks on their CPUs (the language is so vague that you could argue that running non-CPU benchmarks, or benchmarks for other software unrelated to Intel would violate this license). So you can't really make a "choice between performance/security", because nobody is allowed to publish data that would let you make an informed choice.
While still in academia I wrote some code to extract some data from images. It took about a week before I was happy with it. We then decided to make it available for other people. Polishing it until somebody else could use it with reasonable effort took several months and a team of students. That is time that could have been spent writing more papers. It is not at all clear whether enough people actually use the software to justify the effort.

Researchers aren't paid (and usually aren't trained) to write software that can be installed on more than one computer. I don't like that situation either, but that how it currently is. Research code also suffers from accelerated bit rot. The dependencies are often research code themselves and projects are abandoned when the results are published.
Also, wasn't this practice (i.e. engineering to fit design goals) what made Apple successful in releasing the iPod, iPhone, etc?

I am an engineer but welcome the perspective of designers and believe anyway that both need to work hand in hand.

In the case of driverless vehicles however, I am not sure the focus should overly be on design because this is a very hard problem that has yet to be solved, and maybe there was a way of designing a vehicle that was evolutionary rather than revolutionary, while mostly focusing on the technical challenges that must be overcome to get us to autonomy.
what went wrong? declining share price... oh ok thanks.
Your statement is far too broad and lacks context. Where is this a violation and where is it considered fraud? There must be some countries where this isn't the case or at least where the article and non-commercial use of the technique are considered to be mitigating circumstances.

Also, who doesn't find it cool? You don't seem to be saying that what is described in the article isn't cool, you seem to be making a broader claim that copyright violation and fraud aren't cool.

Lets assume you find what is described in this article copyright violation and fraud, because after all, you said it is. Apparently some people on HN find what the author has done cool, judging by the comments. Ergo, some things that you, specifically, consider 'copyright violation and fraud' are in fact cool.
This thread is full of valuable advice, and you should probably bookmark it and read all of it again at times. But if I had to pick a single advice as the most important one: lose the term "rewrite". It's way to easy to get a deadline or time budget attached, and that's a very bad place to be in, especially if people start to think the rewrite stalls regular development. Improving an existing codebase is not a task, it's a process. You make it part of your everyday routine, deliver features on the way, and your budget for improvement is virtually unconstrained.
In that case, just not using useless thing like "back" button will be perfectly fine.

A good website don't need using this button.

And to navigate between websites, using a tab for each website is fine. Especially when comparing results from Google.
"The Government remains committed to the IPO of Saudi Aramco at a time of its own choosing when conditions are optimum."

Not much of a denial.
Seems like a wee bit of a jump to suggest purposeful, direct deception regarding the large-scale history of the cosmos and all of life on Earth.
They de-indexed the domain. I think they do do this on an individual basis from time to time, especially with sites distributing (links to) illegally obtained content.
I believe you are referring to the DeWitt clause.
Good thing we still have a somewhat anonymous internet. I'd be surprised if there wasn't a benchmark or two on the HN front page by tomorrow.

Might even come from a media organization if their lawyers deem this sufficiently unlikely to be enforcable in their country.
That's a surprising thing to say, given that software engineers are always in demand, companies are complaining they can't find candidates and yet salaries aren't growing at a high rate.

Companies like Google, Apple, Intel and Adobe even broke the law and colluded to keep SW engineer salaries down and then paid a pittance when they got caught.

And SW is an abnormally in-demand field. According to HBR "Since the early 1970s, the hourly inflation-adjusted wages received by the typical worker have barely risen, growing only 0.2% per year" in the US.

So not only is the market not fixing anything, sometimes even the law is not enough.
Many subtly and less subtly wrong ideas, mainly the misconception that thermodynamic entropy is somehow different (more "physical") from information theory entropy, rather than its application to a specific type of system (atomic vibrations with the accompanying special concept of temperature).
Not disagreeing with the sentiment, but your point about high availability is not entirely accurate. It's 3 'containers' required, meaning that if you were using Kubernetes etc, then you can have multiple services be HA across 3 hosts. Uptime monitoring etc is just config built into the service deployable.
Chagas disease from 'kissing bugs' is spreading, causing heart issues
Lightweight Linux Distribution Bodhi Linux 5.0 Released – It's FOSS
I don't agree with the first part. I have worked enough time on the management side to understand that management is always driven by business value (it's their job). So your point 'Let new [...] drive your changes' is valid to some extent. But business value doesn't always mean that you need new features to justify working on a project. Sometimes it is possible to justify working on something just by explaining technical debt and how much time it will cost in the future (e.g. slow you down).

Working in an unstable environment can drive you crazy as a developer and lower your productivity enormously. So if you don't talk about the issues in the code base with the management, they might wonder why you have lower output then others and classify you as a slow programmer.

Instead, I think you should bring the facts to the table (slow down factor (number of bugs, time to trace them down), risks (likelihood of production issues)), in terms of how much time it costs to work within the current code base and let the management decide on how to proceed (make sure to bring a recommendation). If they are willing to let you spend time on improving the quality, try to modularize it so that if the rewrite will be stopped at any time, the time you spend refactoring it helps you in the future. While doing so, show respect to the programmer that worked with that code base in the past (even if she/he create that mess). You don't know under which conditions she/he had to work, how she/he learned to programme or what her/his life looks like outside the job.

The management basically has these options:

1. just minor changes to the code base: no rewrite, no hidden quality enhancements (might be a valid option if an alternative software is being developed already).
2. hidden improvement: no rewrite, but you are allowed to spend some extra time to improve the parts you are working on.
3. restructuring of the code base and systematically writing tests for different modules (recommendation).
4. complete rewrite: unlikely to happen unless it is cheaper than 2 and 3.

If the management decides to continue with option one or two, do the best you can under the circumstances be pragmatic as caymanjim wrote. Make sure to include option four so that the management sees the full spectrum of options at hand.
The mind boggles. This is just a bad idea, it's not even interesting...

> Code style is an inherently subjective and difficult thing to judge

wat.

Why would you want an opaque probabilistic style checker...
To name Koreans as an example is disingenuous. If you read the Wikipedia article you will also see that the problems come from both sides. The Koreans the Wikipedia article talks about do not want to fully integrate - they insist on their Korean nationality and demand rights of both Korean and Japanese nationals. At this point in time they have managed to obtain a special status that is the opposite of being oppressed and is actually a source of irritation among Japanese I know. As anectodal evidence to counter your claim, in the Japanese company I work for (in Japan), my direct superior is Taiwanese, one colleague Korean and another Malay and they are all treated like any other.
Researchers have observed the Lyman-alpha transition in the antihydrogen atom
>>So we have inspectors of inspectors and people making instruments for inspectors to inspect inspectors.

When money dries out, sometimes these things take care of themselves.

When India liberalized its economy in 1992, all of a sudden there was a sudden spike in growth of private companies. These companies had a little higher rate of productivity and accountability than most public sector companies.

With increasing competition on both price and quality end, most of these bankrupt companies came to realize that their organization was basically a pyramid with the actual contributors being few and were at the base, whereas there were layers and layers of people in the pyramid all of managers and supervisors of some kinds whose whole jobs was to pass on memos and monitor attendance.

There were huge purges. Mass elimination of jobs followed.
️ Represent any GraphQL API as an interactive graph
> Is the L1TF mitigation actually a lot worse than I thought, or does this license apply to the earlier Spectre/Meltdown patches, or is Bruce Perens just being sloppy and conflating the two?

He isn't being sloppy. According to the Debian package maintainer[1], the new license only applies to the new patches (ones after 2018-08-07) which were released long after the Spectre/Meltdown ones -- because the license was only changed in the 20180807 microcode update (and because Debian didn't block the previous Spectre/Meltdown releases over license concerns).

In theory, nobody can actually tell you how bad the L1TF mitigation is because of the new license terms (a comparison before-and-after L1TF mitigation would be providing you with comparison test results).

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906158#14
Microkernels Really Do Improve Security
I'm curious to know how valid this is in EU countries. Anyone know?
It’s as though Intel is being sabotaged from inside. Delays with 10nm, suspicious exit of Krzanich, harebrained unenforceable licensing schemes. My next machine will use Threadripper and this kind of shit just seals the deal.
Here's a hard earned tip. The first few months, nobody's going to expect much from you anyway. Try to stretch the time you're 'getting up to speed with the code' as long as possible. But in that time, write as many tests as possible. Don't tell anyone unless they ask; if there is no testing culture, they'll think you're just wasting your time on it. Then at some point you will be expected to start delivering value. At that point, you can start making changes (refactoring where necessary) without fear. This will let you grow your status in the organisation until you have a reputation of being the guy that can get things done and doesn't complain about how bad everything is and how everything is someone else's fault when he's assigned a task. At that point, you can start making others write and maintain tests while you take control of keeping oversight of improving the code base quality.

Do not be tempted into 'rewrites' because you're setting yourself up for failure.

It's a long play, yes. If you're feeling the way you describe just from the current state, you're probably not senior enough to do it. It requires much more than just technical skills - those are abundant, it's not what you can build a career on. It's a bit Machiavellan, I guess, but in the end, everyone wins - but you need to have the Vision that others are not able to understand, so you have to find ways to make it happen anyway, in adversarial circumstances.

Good luck.
Avoid lexicographical comparisons when testing for string equality
Two thoughts came to mind when reading this.

First, remember trust is normally earned, rather than assumed. There is a careful balancing act between getting to know the code base, the culture and the team vs being proactive from day 1. If they're completely lacking tests, write tests for the sections of code you're working on; the sections you fully understand. There's a few books on the subject, but they all boil down to don't try and tackle everything at once. Build an understanding and ensure new code is well tested.

Furthermore, make sure you understand the background. Is this a prototype that has been deployed to production? Is your colleague a "starter"; great at shipping new ideas, but stability and maintenance are not their strong points? Do they simply know no better? Why are things the way they are? The solution varies a lot.

Lastly, age, experience and knowledge are often confused in this industry; try to keep them separate. I manage a team of 6 and I'm the second youngest member (late twenties), but the most experienced in my product. It takes a mix of everything to make a good team.
You could offer to pay them today, yes. And get a license. But is your license that handles your use case today still going to be valid and useful a year from now? Five years from now? What if redislabs decides there are some more loopholes in need of closing?

I'm not a fan of the AGPL. I think it's problematic as an example of copyright maximalism, and I think it's counterproductive in that it basically took a bunch of ideas that used to be FUD and said "yeah, what if we actually did that". But I can say this for it: you know what you're getting and you know that for all the burdens it puts on you, it (like the GNU GPL) was designed to make sure certain rugs can never be yanked out from under you.
Dim Sum: Joy Luck Palace (Sunnyvale). LA, the one that’s very good is Five Star Seafood (SGV off of Del Mar). 888 in Valley a little east of that place. Don’t go to Elite, Ocean Star, or mission, IMO. They are kind of on par with Jou Luck Palace. Koi Palace(Daly City) and Flower Lounge(Millbrae), Mayflower(Milpitas) I would stay away from.

Seafood: Newport Seafood(SGV). The restaurants listed above are decent for the Bay Area with Mayflower a notch or two below.

Best Taiwanese street food: Sin Ba La (Arcadia).
Southland Flavor Cafe(Cupertino)

Lastly, in LA, the 626 Night Market is lots of crazy street food.

(Bistro Na is great too.)
There's a bigger difference: Steam competes on "open" platforms (i.e. the major OSes), where "open" means anyone could launch a competing service (and I fully expect another one to challenge Steam in the near future considering the way Steam is heading).

No one can launch a competing app service on iOS. Apparently you can on Android, but I'm not sure why no one succeeded yet. Maybe the same reason as no one succeeded yet replacing Steam either, you need some kind of critical mass and that takes time to build.