skysight-inc/HackerNews huggingface dataset:
Seeing bugs like this reminds me of how much nicer things are on x86 where JITs do not need to flush caches. You can actually modify the instruction immediately ahead of the currently executing one, and the CPU will naturally "do the right thing"[1] --- it does slow down execution, as the CPU is essentially automatically detecting and flushing its cache/pipeline, but used sparingly can be a great optimisation. The write can even come from another core ("cross-modifying code") and everything will still work. Someone I know used this to great effect in squeezing out the last bits of performance from an application by eliminating checks on a few flag variables and the associated branching in a tight loop --- it simply "poked" instruction bytes from another core into the loop when it was time for that core to do something else.

[1] With the exception of pre-Pentium CPUs, where modifying at various forward offsets from the locus of execution could give insight into how big the prefetch queue is. With the Pentium it was fully detected and the later multithreaded/multicored react similarly to cross-modifying code as described above, which leads me to believe that Intel is very much supportive of these things as otherwise they could've just told programmers to do as ARM does.

Maybe what ARM needs, short of doing it the Intel way, is a "flush region" instruction which takes both the address and size, so it can automatically flush the appropriate cache lines based on the current hardware's cacheline size.
Exactly. Timing is of utter importance. Yet, these packed formulas do help to increase the odds of success, don't you agree?
This is a bit like the beat "quantization" options in music apps, where you tidy up the raw user input. The best result comes when you choose not 100% quantized.

The Pix app needs a slider so you can choose how much stabilisation you want on the target part of the image.
It's all made up words anyway, who really cares?
Not sure if any of these stats are valuable.
735 of these entries are errored (no idea what the data is)
2443 are for iPhone 7
3293 are for iPhone 7 Plus

I doubt any of the other data is of value, not sure how valuable that is at all.
I wonder how many other people in the hierarchy of that product (or really, any other that met a similar fate) would cast the blame on themselves. Especially with the legacy that Google Reader has left.

That said, I wonder the details of why it was discontinued (the gritty details available to the final decision makers) and whether those same people who blame themselves today might still have decided to discontinue it had they had the total picture.
Sure, but wouldn't the complexity of managing distributed authorized_keys be significantly higher than propagating revokedkeys across a fleet of servers? You get the benefit of central management/administration with the benefit of distributed ssh keys. It's almost the best of both worlds.
That looks fantastic, I'll take that any day over an ORM in JS.
Makes sense. I missed that section, much clearer now, thanks. Any plans to release more details on how the bastion hosts are configured? Seems like that would be the complex bit to get right.
I am reminded of a Jack Vance quote, where one of the characters is "capable of performing complex calculations in his head and furnishing the results in an instant, whether they are right or wrong".

I cannot find any reference to handling of soft errors in their material. One rather banal approach is to do everything twice and check the results; effective, but I'm not sure that they do this. They may be simply putting their heads in the sand.
+1 for not understanding sync. Was also looking for a way to sync transactions from bank account.
Sex is natural, essential to the continuation of the species. You cannot say the same for killing humans. Butchering cattle, well, maybe that's necessary, but slaying a man or a woman definitely is not. People are advocating to ban death sentences, yes?
In my experience, Chrome seems to be highly biased to matching the beginning of titles (and URLs). It really doesn't like suggesting based on a match deep in the title until you add something like the tld or the site name which often appears at the beginning of all titles.
Re #1, PATCH is useful because PUT requires that you replace the entire resource even if you just want to change one little thing and to do that safely, you need the now-current-latest representation of the full resource. A common case is looking at resource A, which is related to resource B (and therefore you have B's ID, but not its full data), you can patch resource B specifying just its ID and the change that you want to make without having to fetch the whole thing first.

Also, PUT can conflict (or overwrite changes) if something else has altered the resource since you fetched it. PATCH is more granular, so you can make it a lot less likely to conflict or overwrite (in addition to being more efficient).

Re #2, I don't know about consensus, but usually when I think that I could use a custom verb, some more thought reveals that I could instead use a standard verb on another resource that I haven't spec'd out yet (like the comments about having a 'transaction' resource representing details of a transaction instead of a 'transfer' verb).
The Internet Archive would be the perfect group of folks to archive code.
But not referred to in the article, which I found surprising since they're such common terms for those in the know. :)
Fascinating thing I saw recently in social media, though I don't have a URL: Woz woke up one night in 2014 with the thought of a way to knock a chip off the Apple II's design. I haven't looked at the details but of course this was very endearing to me, the pure love for that design that Woz has always felt.

https://groups.google.com/forum/#!topic/comp.sys.apple2/iiLg...
> The blacklist approach means you need to make sure you know of every single possible URL scheme that may possibly be supported, and evaluate every single one of them to determine if they should be blacklisted.

The whitelist approach requires the same thing, it's just that the consequences of getting it wrong are different.

If you don't blacklist something that you should then you could let through a security vulnerability.

If you don't whitelist something that you should then the developers of that software have to devise a way to disguise their software as something that is already whitelisted or be destroyed, which is even worse.

Because doing that is inefficient and complicated, which is the recipe for security vulnerabilities, and then you can't even blacklist it if you know you don't need it because it's specifically designed to parse as something on the whitelist.
Absolutely nothing special about them. They trust the same LDAP/Kerberos infra the laptops are part of. We have two-factor authentication, which is pretty simple with PAM. And they're only accessible if you are in our corporate network.
The problem is that OS X Finder tries to support both Spatial and Browser modes. It has never separated the two modes properly, going all the way back to OS X 10.0, and as a result both Spatial mode and Browser mode are worse for it.

> From small details (like EVERY window remembering exactly how you arranged it) to not having to wonder what will happen when you click something

The problem is that Finder tries too hard to remember window sizes and positions when in Browser mode. Finder doesn't have a configurable browser window size. Instead, it stores the window size and position in each folder. So when you browse around to different folders you clobber any existing settings those folders may have had.

Try this: create a new folder on the Desktop and open it. It will be the non-configurable default Finder browser size that is way too small. Now use that browser to navigate to your home folder, etc. You've just clobbered your home folder window settings.

As a result, you never really know what size the Finder window is going to be when you open a folder.

OS X Finder needs to do the following:

- Embrace the differences between Spatial Mode and Browser Mode. Allow the user to choose whether they prefer Browser Mode or Spatial Mode. Command+N always opens a new Browser Window.

- Completely separate Spatial view settings and Browser view settings.

- A Browser window shall never affect the Spatial view settings for a folder.

- The default size of a Browser window needs to be user-customizable, and it must use the user's preferred size for every new Browser window. The size of the Browser window should never be dictated by a folder's Spatial window size or position.

- Provide menu items and keyboard shortcuts for the "Use as Defaults" command for setting the default view settings, as well as for reverting a folder's custom settings to the default view settings. If I enter a folder that has some goofy custom font sizes or column widths, I want to be able to hit a key and have it snap to my preferred layout.
Hardware support is also one of the reasons to keep using OS9. I still use it on a 1998 Powermac almost every week as my drum scanner requires a custom PCI card and an app that ties everything together. Its vendor went under long ago and so no one to port their app to OSX. Works like a charm, with original keyboard and mouse.
It doesn't seem like it's more work, although you are right in that it's probably more user friendly as you don't have to wait for keys to propagate to various servers before you can login. We've previously used a cron script to pick up authorized_keys from a centrally published source, I guess that same infrastructure just moves to the CRL.
Sure but Facebook isn't preventing the media from showing this, sure if Facebook was our only forum for journalism censorship of things like this would be atrocious. But I don't think facebooks argument is this shouldn't exist but that Facebook isn't a news station and isn't the right forum to share those kind of things. One easy reason is news stations warn about graphic content and are usually watched by adults whereas any 10 year old with an internet access can find it on this guy's Facebook page. I think this article, and the outrage in general, treats Facebook as too powerful of a social institution. It undeniably is but I feel it's influence is overstated, and that Facebook trying to maintain itself as a forum for socializing is fine, it owns the website it can decide what to put on it. If the thing you need to say is so important there are many other forums to express that idea, even within the internet. That said I think if this truly is Facebook is trying to make a policy that truly promotes what their trying to do it should be stricter. Videos of beheadings belong on deeper webs imho.
Cool. I understand what you are saying.
Thanks for taking the time to reply!
I've always felt more persuasive when doing that.
I've also felt more persuaded when I'm not flat told I'm wrong.
Hypothetically, with PUT, whatever you send to the server should now comprise the entirety of that resource. So if all you PUT is a last name to /people/4335, then all of a sudden person 4335 consists of nothing more than a last name alone in the void, and not even blank fields beside. With PATCH, on the other hand, you can confidently send the value of just one updated field, without your users worrying about their metaphysical well-being.
Dry rub is good too :D
I've tried nvim, sublime's vintage mode, atom's vim mode, visual code's vim mode, jet brains' vim mode, spacemacs and always end up going back to vim. I know it's far from being perfect. All of those other alternatives have features I wish vim had but at the end there's just no comparison against the flow you can get with something like tmux/vim/plugins
That place should not be a company which is known for not fighting against DMCA requests, and requires that users run proprietary JavaScript. The best place would be the Internet Archive, hopefully running an FSF approved Git front-end (GitLab or GNU Savannah -- Gogs is probably also fine but they haven't reviewed it). Nothing else is acceptable if you actually want to make sure that code will truly outlive us.
The bubble screen is terrible, but at least in watchOS 3 you're supposed to almost never have to use it.

It's one of those interfaces that looks great in the video and it's horrible to use in real life.
Most people don't succesfully change diet over the long term.
Interesting! I looked quite a bit to see if there was anything OSX-specific that anyone else online had documented, but nothing I turned up seemed to pan out. I am reasonably certain that the ultimate culprit here is bad low-end wifi devices that either suffer from bad hardware (too little RAM, etc.) or bad software (some poorly tested customized version of embedded Linux), or both. But I'm really curious why only OSX seems to cause the problem to manifest in several of these cases.
While I don't know if my snow balls will go anywhere, one thing I've noticed is that many (most?) successful entrepreneurs have a high risk tolerance. I went to a meetup where Alan Grant (Hired) talked about his tolerance for risk- sometimes it even involved activities on his part that were a violation of TOS. The point is sometimes to do creative destruction you have to get your hands dirty. Try to maintain a "chaotic good" alignment if you will ;)
I don't know of any other application-independent image format with good support for layers. Seriously. (Even Tiff doesn't really have good support for layers.)

.PSD is tightly tied to Photoshop's internals, and .xcf is tightly tied to Gimp's internals. (The Gimp core developers explicitly recommend against using .xcf as an interchange format, even though the format has a fairly complete publicly available spec.) I've seen .gif images with multiple frames used as images with layers, but that forces every layer to have the same resolution, and of course limits you to an 8-bit color depth.

Supposedly the Gimp and Krita devs are collaborating on a new interchange format that will support things like layers, but I haven't heard any news about that in years.
Can't agree more.
Not OP but a lot of this seems pretty believable and easy to detect to me?

Dont the GPU specs allow for a certain lossiness in the math? Or like, at least they don't conform to IEEE 794 float specs w/ regard to order of operations, precision, degradation, etc.

So like, do a shitload of math ops in a glsl shader with a deterministic outcome, render the result to a texture, take the texture back and make sure the RGBA values match bit for bit with the numbers you expected?

Or to detect single bit errors in the gpu's local memory or caching just attach textures, read data into them, read it back, render back, etc etc.
TreeStyleTab really just blew my mind. I think it's the straw breaking for me to go back to FF.

Seriously, tabs on the side in a tree view make SO MUCH SENSE!

I know many of you probably have a few dozen tabs in chrome open, and you gotta guess whats what from the icon. We keep making monitors more widescreen yet webpages mostly need a max-width. I'd bet in the next few years all browsers will switch tabs to a treeview like this.

And wow, the chrome extensions trying to do the same thing are fugly as all getout.
Presumably the fact that they take down repositories that disagree with their politics (or the politics of other governments). They also don't appear to put up any fight against DMCA's, and they mandate that all users must run proprietary JavaScript. LibreJS makes the site mostly work though, so it's not that bad. The biggest problem is their policies, which are not pro-free-software (no matter what they might say).
Nah, sunsite is a noob, along with Slackware. When you wanted to download boot/root, Tamu, or SLS you went to tsx-11.mit.edu or ftp.funet.fi to get it.
Sound and well written advice; however, I would add: don't expect your snowball to reach über size. There are tons of problems to solve/improve but the great majority of them have a small market size/potential. The big markets are too hard to disrupt.
Many years ago, one place I worked at had the following setup: a closed source application would generate a CSV file, which was then FTPed to another server, where a Perl script translated from CSV to fixed-column-width format (which happened to be identical to the output format of an old mainframe application that we'd migrated off), and then the fixed-column-width file was FTPed to yet another server which loaded it into a database. Now, the CSV file had a number of fields - name, address, etc; but it also had an encrypted password field. We didn't use the encrypted password for anything, we didn't even know what format it was in (hashed or reversibly encrypted or so on). The CSV format was fixed by the vendor and we couldn't change it. However, rather than being output in Hex or Base64 or similar, the closed source app just put the binary data of the encrypted password into the CSV file, which would randomly contain comma or new line characters. The author of the Perl script wasn't aware of this possibility, so the Perl script would die, complaining it had got an invalid input line (wrong number of fields), whenever that randomly happened (sometimes several days in a row, other times it could go weeks without happening).

I proposed to modify the Perl script to fix this issue. However, management refused to let anyone modify the Perl script. The guy who wrote it was a contractor who had moved on years ago. This Rube Goldberg file conversion and transfer formed part of a critical business process. A couple of years earlier it had failed, and its failure resulted in bad press and reputational damage. So they were way too scared to let anyone modify the code of the Perl script.

Instead what happened, was each day a person would manually check if the script had run successfully the previous night. If it did, they'd fix up the data issue in the input CSV file using a text editor then manually start the Perl script again. Management agreed that we could automate that checking process, and if the Perl script failed they would get an alert on our service availability dashboard. But no way would they let anyone fix the bug in the Perl script.
If they are serious, they might want to do it full time. Or even hire people. They'll require funding. Even recruiting people to work on OSS requires marketing of sorts. You gotta convince people the project is cool, but that it's on a good trajectory. And finally, after all this, you want people talking/following so you can push your results out.

There isn't anything inherently wrong with self promotion and often it can be critical.
I used to frequent a coffee shop with a router that would refuse to let my laptop's wifi card connect about half the time. Like the author, my phone could connect but it would simply not respond to any attempts to connect from my laptop, whether booted into Windows or OpenBSD. The only solution was to ask the barista to reset the router, which was all the more frustrating when they refused to do it because everyone else could connect just fine.
> Although I'm not sure how apparent this was in the 30s.

I think in the 30s one could have said, 'fascists have killed their thousands, but communists have killed their millions' (the Holodomor was '32-'33). Even Western fellow-travellers would had to have admitted hundreds of thousands of Russian bishops, priests, monks & nuns — 85,000 in 1937[1], during the Spanish Civil War.

[1] https://en.wikipedia.org/wiki/USSR_anti-religious_campaign_%...
With openSUSE, we store a copy of the source code in our own repos in OBS[1]. And all users can download the source RPMs.

[1]: https://build.opensuse.org/
this is super cool. One big struggle I had transitioning from OS X to Linux was 1password. I ended up using wine with the windows version which was awkward. I love CLI's to this may be a nice solution. Thanks!
For how long?
it flatters the ego, which can be belittling at times.
Your article doesn't mention it: Have you tried using a statically assigned IP address? (Poor etiquette inside the DHCP range, but maybe if you just snarf the IP you've already leased..)

I ask this because OS X's DHCP stack is known to exhibit some strange and unfriendly behaviours: http://cafbit.com/entry/rapid_dhcp_or_how_do
If you have a maintainer who signs their commits, you trust their signatures and call it a day. Go with the latest commit and that tells you the history that they have cryptographically claimed is "correct".
Is the data stored in GPU memory?
Python Insider: Python 3.6.0 beta 1 is now available
> That debris went into orbit, then coalesced to form the Moon. And that raises an intriguing counter-theory: maybe that Mars-size impactor, which planetary scientists call Theia, is the object that became Mercury. If that’s correct, the answer to where Mercury’s rocky outer layer went might not be under our feet after all.

Source: http://time.com/2958731/mercury-peculiar-solar-system/
It would seem that rationalization would fall apart quickly with the new Power CPUs that have NVLink built right into the CPU. Getting data back and forth shouldn't be a problem anymore.

Outside of CPU >> GPU, I'm not sure what other data movement you could be talking about. A SAS HBA or Ethernet NIC or Infiniband HBA are almost always going to be operating over the same PCIe bus the GPU uses. In the rare instances they're built onto the CPU, the "network link" is likely going to still be significantly slower than the fastest PCIe slot.
Finer-grained location permissions
The details are vague but if I remember correctly, this is due to something OS X does with DHCP that isn't quite standard but apparently helps to make connection resumption faster --- when it works, that is.
Show HN: Find your next favourite podcast
oh man... what a vision of the world... I cannot stand these america-centric visions...

One of the things that we talk among the people who keep going to Cuba or have relation with it is the fear of change to what the US capitalism will bring.
Its sad to think about Havana with Mc Donals, Starbucks, H&M, Coca Cola ads everywhere and people just thinking about money and more money killing the amazing and unique culture they have.

Its sad that nowadays, no matter where you go, you find the same, same crapy food chains, same repetitive top40 music, same h&m aesthetics and the same boring hipster coffee culture... and not forget about hamburguers and bacon everywhere... the american dream!
I wouldn't say Windows Phone is the worst. It performs well on low spec hardware, it gets updates, and the Nokia lineup provides better value than equivalently priced Android phones.

Disclaimer: Posting from my Lumia 640
BlazingDB GPU Database
Always start from common ground and that which can be agreed upon.

Although I do disagree that there was no formal study of "persuasion" before then. Socrates was trolling sophists long before then. Rhetoric = persuasion and thats what the sophists got paid to do.

Read Gorgias.
From a straightforward standpoint, having to think about how the other person is right, and then to incorporate in a rebuttal, simply takes more time. Which for me is helpful because that physical delay curbs the kinds of reflexive emotional responses that I regret later.
Step one: climb mountain

Step two: build a little snowball

Step three: give your little snowball a little push

Step four: fret about which direction your growing snowball is going
Because that's the loophole the government needs to attempt to limit export of it. Why does the FDA want to class inflatable pools used for water births as "medical devices" that need millions of dollars in studies before they can be sold and used, but on the other hand class stainless steel operating tables as not medical devices?
Slack also has an amazing UX, I haven't used a competing product that was as enjoyable to use. Yes I know this is subjective, but of the people I know that like Slack actually love it. Whereas I've never met somebody that loves HipChat.