skysight-inc/HackerNews huggingface dataset:
What magit offers over the CLI, in the area of reworking commits, is actually rather spectacular. It's more than interactive rebase -- it's e.g. the ability to selectively stage individual lines (or hunks or files) and chooose which commit to apply them to as a fix up. It's definitely worth trying as a non-emacs user; if you're interested I can post instructions for starting a one-off emacs instance for magit and nothing else.
> In other words, if you want competitive RISC-V chip, some company must spend hundreds of millions to develop their own RISK-V chip architecture...

I wonder if a country like Russia, wanting something that they can deploy without worrying that the NSA & Intel are cooperating on state spying, will eventually try and take something like this and bootstrap a domestic semiconductor line of business.
A green polka dot jacket.. No thank you.
I like to think web browsers take the worse is better approach to security.

Security takes a back seat to reproductive fitness of the web as a platform. JS made the web insecure, but it also made it the world's premier application platform.

I blogged about this: http://kylebebak.github.io/post/browser-security-worse-is-be...
I had to personally apologise to the IT department because I sent a message from 'God' saying "I saw what you did last night" to the entire network (long time ago but it was Novell something) by mistake (was aiming to send it to just the one computer lab).

They thought it was hilarious and that was the end of the matter.
Yeah salaries are pretty low in Tokyo for a lot of jobs, if you're on the lower end of the skill hierarchy you're going to be in pain.

But ... it's not like low-skilled workers in SF are getting paid much either.

The average HN reader might be in a better negotiating position w.r.t. salaries in Tokyo

Some things to consider about Tokyo:

- No need for a car, insurance that comes with

- Your company will (in almost all cases) be paying for your daily transportation by car

- If you're willing to suffer in the morning with travel/take a bus to the train station, you have a range of prices for renting

- There are a lot of people living on low salaries, so there are a lot of services on the low end. 100 yen shops with high quality stuff, all things considered.

For 60,000 yen/month you can get 20m2 studio appartments (25-year-old buildings) within 15 minutes of stations like Nippori or Otsuka. If you follow the "1/3rd of salary" rule, it's reasonable if you're making a bit over minimum wage (not sure what the going rate for English teachers are)
That makes sense. I think you jumped to quickly to interpreting the original comment as an intent to influence the standard. I read it as just "here is a thought that might be useful/relevant to the people who are making the thing so that they can use it as they see fit when making the standard".

No big deal either way!
> yet many many younger people work for as temps, which is sort of counterintuitive for a very tight labor market.

because many of these temps younger folks are university students at the same time. In japan university is only very few hours of attendance every week, so it leaves them with tons of free time to get a side-job.
I'm using Visual Studio to both code and commit. In there is a "pending changes" window that allows me to cherry-pick the changes I've made and make small consistent commits instead of a big one.

I'm not sure if such a UI exists for other coding environments, but I definitely wouldn't bother doing it if I was using command line to commit.
Tried Dazzle few times this afternoon and this browser is just brilliant.

Why: Currently, user interaction with tabs on mobile browsers is totally broken and super cumbersome. Dazzle is merging browsing history with tabs which is smart and leads to a super smooth user experience. Actually, there are no tabs anymore, just the browser history which pops ups every time you touch the address bar at the bottom. Simple but nice solution.

Moreover, it offers a bigger viewport than Safari does (no iOS navigation bar at the bottom und a black slick and super slim address bar).

Finally, I like the slightly rounded corners of the viewport. All small and subtle stuff but shows that the creator cares about a polished appearance.

But I am not sure about the landing page and this 'first principle' thing. People don't get it and it sounds super awkward. Really remake the landing page, make it slicker, put some screenshots there, remove the first principle blabla, find a punchy headline and remake all the copy.

You should definitely keep on working on this and not let yourself getting discouraged. The product and the minimalistic approach you chose is excellent, the Marekting/branding not so.
If you're using Vim, there's a good chance you're doing it in a terminal. In which case you have all of the debugging tools you could ever need right inside the same terminal.

That's why I (and many others, I'm sure) don't mind that I don't have a debugger built into vim - it's just in another tab.

As for constant type checking, it too is available via plugins.
No matter what happens, someone is going to come out of the woodwork to claim credit for it. I don't buy the narrative that some big hedge fund guy masterminded the whole thing while the rest of humanity stupidly played into his hands.

A more likely scenario is that people already had some theories about globalisation and its negative side-effects and then maybe several interest groups used their influence to help reinforce those ideas through social media. Let's not forget that there were also other interest groups that were trying to promote/reinforce the opposite view point.

I don't fully buy into the echo-chamber argument. I think that by the end of the 2017 US elections, Everyone had a pretty good understanding of both candidates. That was probably the most transparent election we have ever seen. If anything, there was too much information on both candidates and it just made both of them look terrible.
The $3500 board is a lot, yes. There is also a $99 "Arty" board that is enough to run what is in the HiFive1, and I think even to add an MMU and run Linux. The $3500 one has enough space to do multiple cores, FPU and so forth as well.

Both the $99 and $3500 FPGA boards run a Rocket CPU at 65 MHz, which is pretty slow, though faster than you get with a software cycle-accurate simulator on a workstation.
The unemployment rate is actually 3.1% now, and they calculate the rate the same as all the other countries in the OECD.
Each function call is a transformation on the previous argument. Whether or not you assign the results to a variable first before calling the second doesn't change the behavior of the code.

But yes, it does appear that the config library needs an extra wrapper that loads from files and returns configs (in a context) that does the common work for you.
I cycle wearing high visibility gear over a flat base colour, lots of cycling friends wear team gear with different colours and logos slapped all over, it's basically camouflage since it breaks up their outline.
That comes at the price of bad mileage, lower torque and acceleration.

https://www.nytimes.com/interactive/2015/business/internatio...
You could achieve the same thing via virutalization.

Run a small OS first which has remote management capability, and then boot straight into a virutalized OS that the user uses.
Thanks! looks great
CI for Embedded Systems
I think that was one of the proposed variations, but we ended up picking the shorter .expect to cut down on repetition. We expected (ha) that this function would be used in these one-offs, so we wanted something more efficient.
I'll buy a LoweRISC as soon as they have something for sale (and I have one of the first HiFive1s). But at the rate both organisations are progressing I expect to be able to get a quad core 1.6 GHz 64 bit RISC-V "Pi-like" board from SiFive before LowRISC. Possibly even this year. I've gathered from other things they've said that they're sampling wafers with that SoC about now.

Ideally, they'll both succeed.
I'd go the opposite direction: commit as often as you can. Ideally after each micro-iteration, when something new is working.

This way, at the end of the day you can just rebase the whole branch and squash all of the micro-commits in a whole commit implementing the whole new features.

It's nothing fancy, just rebasing (which is very very easy in git).
Pretty neat. Would be useful to be able to restrict the blocks that are searched. For example I might know that the character I'm looking for is Japanese, so if I could let it know that I was looking for is Japanese then it could restrict itself to Katakana, Katakana Phonetic Extensions and other blocks if any that apply to Japanese specifically.
Thank you for changing the source. Seeing a science article from Buzzfeed on the front page of HN was pretty unsettling.
Homophobia isn't excusable no matter what position the target holds.
Algorithms are failing Facebook. Can humanity save it?
Of course keeping in mind that a "far suburb of Tokyo" will still have a population of 400,000 or so, roughly comparable to the size of Miami or Oakland. Yokohama is definitely not Tokyo, but its population is 3.7 million, larger than Chicago and just a bit smaller than Los Angeles.
One day, a machine will smell your weakness. Then it will come for the kill.
> Present and former industrial workers basically all voted leave, while knowledge workers and finance voted remain.

Do you have a source for that claim?

According to The Australian:

"Leave was backed by almost two-thirds of those considered “working class and non-workers”, meaning skilled manual workers through to those with lower grade jobs, pensioners or welfare dependants."

http://www.theaustralian.com.au/news/inquirer/brexit-who-vot...
> Better source from UC San Diego:

Because it isn't BuzzFeed?

I read both articles and the BuzzFeed one was much more extensive, covered both the background of his infection better and the process in which he ended up getting the phage treatment.

So no, your source isn't better in this case.

EDIT: Here it is since the mods swapped it out already, https://www.buzzfeed.com/azeenghorayshi/navy-phage-viruses-f...
800 yen for ramen is standard and has been for years.
> Yes. And like everybody, I have my own priorities, and will not apologise for JMAP not being one of them.

That could have been said better considering he was taking your comment for possible action. If you don't think that comment is a bit snarky, so be it. I do.
>> Examples of elegance in deep learning: The gating mechanisms of LSTMs (also adds to interpretability);

LSTMS amaze and dumbfound me in equal measures and I admire anyone who can understand them, at all.

Could you please indulge my cluelessness and explain to me what is mathematically elegant about the gating mechanism in LSTMs and how it adds to interpretability?
One interesting note in the article: « unauthorized accesses typically aren't logged by the PC because AMT has direct access to the computer's network hardware. »

That's unsurprising now I think about it, given how AMT works, but aren't the sort of companies that would want to use AMT also the sort of companies that have security policies that require all such things to be logged?
That is an asian thing. Im seeing it with chinese buyers in Vancouver. They dont want a "used" house. New houses are being built to low standards on the assumption that any future buyer will rebuild anyway. Give me a 35yo house with a proven track record over some new thing that could be leaking come winter. Houses are not cars.
This article exemplifies something I see novice programmers doing which it would be good to avoid. Basically, it places too much emphasis on "commit". This attitude does indeed lead newcomers to commit rarely. I think the word itself doesn't help; we shouldn't think of it as "commit", but rather "quick painless snapshot". The milestone beginners should aim for is where they commit frequently, and come to see the git UI as the way to change the state of their code (rather than the undo button in the editor!) If reworking commits were easier, people wouldn't think they had to be so perfect and they'd commit more. Magit can solve this, even for non emacs users.
There are important people at Microsoft who basically get very confused about what "x86" or "arm" means. There was a contingent that decided allowing third parties to port win32 apps with a recompile was off the table (despite it being very doable - just look at explorer or notepad running on surface rt), and to this day whenever many MS folks make public statements about windows on arm they sound hopelessly confused.
I agree, all the HN clones that come up are usually just a ton of JavaScript that slow everything down. I've been using my own minimal clone[0]. It uses the firebase websocket API and focuses on speed and readability. The source is here[1] if anyone wants to fork it and create their own experience.

[0] https://hxn.kbl.io/
[1] https://github.com/blopker/HXN
I think we are talking about different things. PGAS is intended to develop more sophisticated parallel LOGIC codes more easily, which is a requirement to handle upcomming MIC hardware. The logic codes itself will play a major role to make efficient use of such hardware and to develop new algorithms for upcomming hardware. I am not against OpenCL or anything else, but consider these as low-level parallelism. The MIC is just starting by now and is very distinct from GPUs. At this time, we are only preparing for the near future.
I have a class next semester specifically on command line and NIX that I'm pretty excited about. When you say scripts do you specifically mean bash scripts or more generally like Python scripts ect.
I have no problems with veterans wanting to become coders. What I don't want more of are people who go into this profession only for the sake of making more money - These people are only driving up software complexity and not actually adding value to their companies.

Software engineering is one of the few professions that let you get more money by delivering a lower quality product (assuming that your manager is sufficiently non-technical).
In that case, it doesn't matter what Cambridge Analytica did or didn't do. So why are you?
> I don't think the comparison works. Choosing the words Simple. Secure. Stunning may or may not accurately describe what the application may be, but it clearly describes the priorities of the designers of the application.

I can see that. I don't think I'd have an issue if this was their mission statement and plastered all over their office walls as something aspirational. But that's not how it is being used here.
Plus the ergonomics and mnemonics of the keys is really nice. You bring up a menu with a keypress, and then the most common command in that menu is typically just a second press of that key. E.g. c brings up commit menu and pressing c again to bring up the commit message writer, or c a for commit amend, etc. For branches, b b switches branches, l l for logs, r r for rebase continue, p p for push upstream, things like that. Then at any commit sha or file, you can move your point to it and hit enter to view that thing. Or just hit tab to see the diff. It's quite nice.
Sounds like an aversion to me. By the time Go was developed, there was no doubt in my mind that generics (or some kind of polymorphism along those lines) were an essential feature for any new statically typed programming language. The fact that Go's developers "don't feel an urgency for them" to me makes it sound like they are living in the 1980s.
Similar story here - mine was in the days of Windows 9x; everyone knew about "net send", but few bothered to look into the other options.

I decided to poke at it and see what "/forest" did, ended up messaging the entire network with a harmless "Hello world".

It's shocking to see the ordeal that mmccaff went through; for me it was just a couple of very confused teachers and an IT department that wanted to keep an eye on the troublemaker.
U3 is standard precisely so that we can compare differences between countries. If people don't like what it's measuring, then they can certainly use one of the other metrics like U4, U5, or U6.
Here Comes Another Discount Airline, and Wall Street Isn’t Happy
It just isn't quite as stealthy if you have to power up the box when it's supposed to be off.

I mean, not everybody runs Windows 10 and is used to his machine having a free will of its own ;)
My favorite level 5 was a bug in clang that caused it to occasionally emit incorrect code when calling a vararg function. However, the bug was harmless when combined with clang's vararg function prologue. When calling a vararg function compiled with gcc, the clang bug would cause gcc's prologue to jump to a quasi-random address vaguely nearby and continue execution in the middle of some other function. That was great fun. I wrote it up here:

https://www.mikeash.com/pyblog/friday-qa-2013-06-28-anatomy-...
Building a list of interesting people to follow is the biggest part. Keep in mind that this is visual communication, so there will definitely be a bias towards photographers, artists, journalists.. Not everyone is able to communicate visually well either, and the format prevents long textual explanations and favours a more emotional response.

National Geographic has a few accounts (natgeo, natgeocreative..), NASA shares interesting tidbits about current missions, Magnum photography has interesting pieces of visual journalism, many unknown journalists use it to explore projects that do not always resonate with current trends in the media/their workplace.. There's decent content on Instagram, although it isn't easy to find.
Why would cooling offer such big performance improvement to DRAM ? even if it improves transistor witching speed, wire switching speed shouldn't be affected and it is a significant component of latency , right ?
You omitted the young Vs old divide.
Codepip – Play games. Learn to code
> In Luddites' case the tech was clearly making our society a better place,

Is what OP said-that is subjective. How is our world, better? Is it truly better? Sure-I have benefited from use of computers, but many people have been killed from use of computers (drones, for example).

It is very possible that all of this technology eventually wipes out humanity, which would not be beneficial, would it? The claim that technology has made society better is a very strong one, which no argument was made as for why.

Your test isn't a proper test. Technology is neutral in the sense that all of the good it has brought, has also brought upon lots of bad. For every piece of technology used for good(missiles for space travel) there is an equivalent use that has done harm. (Cruise missiles, which have killed scores of people.)

I'm not debating that technology had impact-but to say it is all beneficial, is a huge stretch.
Anybody who lives in Manhattan would be thrilled to get a Tokyo-sized apartment at Tokyo-sized rent.
a compiler-guaranteed safe systems language

When I need that, I use OCaml.
It does, but it may sound derogatory because African has a much wider and broad meaning than a specific Dutch word (used in a singular colonized area).
Yes, except I don't recall Obama using big data to blast people's facebook feeds with fake news citations, irrefutably wrong numbers and xenophobic clap trap.

"With great power comes great responsibility" and all that...

This is the problem with the far right (or any political extreme). They're not interested in debate or acting responsibly.

An excellent example was Le Penn's 'debate' a few days ago with Macron. It was a fucking shambles and embarrassing to watch. She had the whole of France watching - it was her time to shine and capture voters with her programme. She failed miserably because other than soundbites, there's no meat on the bone. The FN cannot withstand the sunlight and rigour of genuine, intellectually honest political debate.

They (and all other extreme parties) know this of course and so their solution is to try and debase the system itself. To convert people from reason to "gut".

Given that back drop, yes, it's a little concerning extremists are awakening to the awesome power of big data. Coupled with the delivery mechanism and reach of the internet, it's a propagandist's wet dream and potentially extremely destabilising if left unchecked.
I read about this recently. It's hard to believe these cookies didn't exist until 2016.

The biggest problem solved by cookies has always been sessions. samesite is sufficient for most sessions. It seems like samesite should have been the default from the beginning.
Yeah, I remember a time when I never used to remember to commit at the right places, and I'd end up with a pile of work I had to laboriously sort through. I ended up writing a little bit of VimScript that helped me get into the habit of committing in the right places.

The crucial idea is to make the changelog a first-class file that I can see and interact with in my text editor alongside my code. As I bounce around my text editor, the changelog keeps popping up in front of me, making sure it's never too far from my thoughts, and encouraging me to write in it. Everytime I save the changelog, editor automation records my latest update to the changelog as a new commit message. The changelog now becomes conversational, a record of my thought process as I work through a problem. Commit messages go from cacophonous to harmonizing.

Over time I stopped needing these training wheels, but they were very helpful for a couple of years. More details: http://akkartik.name/codelog.html
I don't plan my commits. I start writing whatever seems necessary. It's kind of impossible to draw a map for a terrain you haven't seen yet. If I feel like, ok, now it's time to record what I've done, I use `hg commit --interactive` to pick apart my working directory into relevant things using a very pleasant curses interface for diff selection. I can always later on `hg amend` any commit that I think may need it.

Then there's the awesome `hg absorb` that will let me amend a whole stack of commits at once, automatically. It figures out which commit on earlier in my stack should get whatever change is in my working directory and automatically cherry-picks the right fix from my working directory to the right commit.

http://files.lihdd.net/hgabsorb-note.pdf

If I need to change gears, I make a temporary commit, labelled by some bookmark, and move to a different branch of my repo. If I want to throw out part of my working directory, I use `hg revert --interactive` or `hg shelve --interactive` depending on how permanent I want the throwing out to be. This uses the exact same curses interface as `hg commit --interactive`. I also rebase (i.e. change the base only, not rewrite the commit), fold/squash, and edit commit messages, authors or dates as needed. The best part is this all propagates metahistorically via changeset evolution (available now as an open beta on Bitbucket). It's all really nice, and I wish all of the Mercurial workflows for polishing commits were more well-known.
There is a a guy being charged for burning, or threatening to burn a quran in Denmark right now.
At least for me, :%s/foo/bar seems to work fine, as does the find command.

I think that registers should mostly work pretty well too ("ayy and then "ap work fine for me).

I don't know if this is what you're talking about, but we have some ctrl+d/ctrl+u bugs that have to wait for upstream changes :/ https://github.com/VSCodeVim/Vim/issues/1348

I saw that you said you'll submit bugs to the tracker, so I'll see those then :)

We've been pretty active about adding features/fixing bugs:

https://github.com/VSCodeVim/Vim/releases
It sounds like you didn't read the article. At the least, your comment doesn't address the main issue presented in the article: that the Brexit vote was heavily influenced by non-UK interest groups. The article presents a pretty solid case, with plenty of evidence of foul play.
Self-made millionaire: Don't start your own business–unless you have this trait