skysight-inc/HackerNews huggingface dataset:
My thought about the touch bar is that it starts to tackle a problem which began in the 1990s once desktop displays hit 1024x768 pixel resolution and has only gotten worse as displays pushed to larger and larger size.

Namely: the display was originally small and easy to mouse all the way across, meaning the menu bar and toolbars were always in close reach, and moving the mouse from the current position to the menu bar and back was fast and precise and not too disruptive to work with the pointer.

As displays grow, the menu bar, toolbars, and other on-screen non-content UI controls keep getting further away and more disruptive to reach for with the cursor. If you frequently need to precisely mouse across a 30 inch display, click a button, then precisely mouse back to where you started to carry on with a content creation/editing task, you’ll start to hate performing that action and look for ways to avoid it. But often there are actions which can’t be handled by keyboard shortcuts, or software with so many functions that remembering the keyboard shortcuts is a chore.

The original justification for a fixed-position menu bar at the edge of the screen was that by Fitt’s Law, it would be very predictable, efficient, and cognitively easy to navigate menu options. As software gets more complex and displays get bigger, that justification starts to break down.

The touch bar is a way to restore the fixed-position nature of the original menu bar and even improve on it, moving tools off the virtual screen and into the physical space of easy-to-reach direct finger touches, letting someone drive a contextual toolbar while hardly moving their fingers off the main section of the keyboard.

I haven’t seen anyone else try to seriously tackle this problem on a desktop/notebook. Certain niche software has adopted gesture interfaces or radial menus, tried to cover every possible command with keyboard shortcuts, or adopted something like the Quicksilver/etc. command-line-with-text-completion UI, but usually the usability of all of those for non-experts has been poor.
Has anyone read the FAQs? Littered with misspellings and common grammatical mistakes. Screams in[secruity].
You can check here how they manage to do that https://www.youtube.com/watch?v=069y1MpOkQY
You want to switch time to base 10 and everything else to base 12 even though you consider it to be arbitrary?

We use 12, 60 (and 360deg) because our fingers are divided into 12 sections on the palm side.

You can use your thumb to point to each section on your right hand, counting to 12, while using the number of fingers on your left hand to keep track of how many 12s (up to 5) hence base 60.
Bypassing Two-Factor Authentication on Outlook Web Access
ISO, and many places, yes, but not everywhere. Is it necessary to add "At least in the civilized world"? Seems unnecessarily inflammatory. And the gp is proposing a new system anyway.
https://www.reddit.com/r/golang/comments/5alxa3/gos_alias_pr... points out that this isn’t actually a problem that is specific to Google, but rather affects the FOSS community as a whole, and I think the recent move of golang.org/x/net/context into the stdlib (as context/) is a perfect example.

The author of the article doesn’t seem to mention or consider this point at all.
> the idea that emotions are not information

> signaling that one is upset

I think you're missing the point. This is a way for people to claim that they won't be offended (and won't start a flame war--remember those?) and thereby invite others to speak plainly. The belief is that this leads to a more efficient communication than people not speaking plainly for fear of offending you.

There's nothing in it about ignoring other people's emotions, not expressing your own emotions, not being empathetic, emotions not being information (the post literally says the opposite of this), or pretending to be emotionless like so many Spocks. I think all of these are things that you're reading into what's actually there.

> one should offer to be receptive to empathetic discussion about a difficult topic.

An important part of that is letting the other person know you aren't going to jump on them for something they say. This is what Crocker's rules are about.
Yet there are existing solutions to the context issue, namely vendoring and versioning, that work well for OSS but don't work for Google.

The alias change could be useful in OSS, but it's certainly most useful in a monorepo.
These are on sale at WalMart in the US. Indo think they're rather new there though.
Can you point me to the page you found these on?
Short replies coz on phone.

1. Async await is almost similar to normal looking threaded code. Just add await before a normal looking call.

2. A language could have chosen to make it "exactly the same" by auto inserting awaits, but then you don't get to say when you don't actually want to wait. Many times you don't.

3. I agree native threads are cheap. But you still have a) thread stacks and additional control structures, b) wouldn't you have to deal with things like processor affinity? I mean, either you/lib or the kernel. And the kernel already does it for you.
It's the age-old cartesian dualism between reason (good!) and emotions (bad!), which for some reasons still seduces many people. They believe they are more or less their pre-frontal cortex, so things like emotions get in the way of the Thinker.
Maybe it's updating its servers to become a protocol
The CC0 page[1] on the Creative Commons website is in the Public Domain section and describes CC0 as a method of contributing works to the public domain.

1. https://creativecommons.org/share-your-work/public-domain/cc...
As long as you're not attempting to buy or sell, correct.
OBS does, OBS studio doesn't.

It's replay buffer where you start the replay buffer and it will keep the last n seconds of footage in a buffer. You set a keybind to save that buffer to file.

https://obsproject.com/forum/resources/obs-classic-how-to-us...
If making comments invisible is at all helpful, they’re being seriously misused. Comments are supposed to explain what’s going on, and thus make things easier. Hiding them should be very counter-productive.
Good, one of Go's strength is easy refactoring given that the standard library includes its own parser and syntax packages. If something gets renamed, just write a small script to replace all references...
This sounds interesting, but I'm skeptical. 12, 60, and 360 have nice mathematical properties independent of human morphology. Do you have references to cite this?
If it's efficient for the hydro setup to use wind for heating, why not the rest of the village? My point stands?

A better example 'might' be plants can take random times of darkness in their stride so random blackouts don't matter. But given the high cost of the setup I doubt you'd want to screw with efficiency.
Great resource.

Can somebody recommend similar resource with unprocessed images? Most photos toned or converted to black-and-white.
SSD and GPU are quite a bit faster, the CPU isn't, but it got more power efficient and is more of an Intel problem at the moment as they are focusing on that.
Apache Spark: A Unified Engine for Big Data Processing
He is listing the size of the new MBP vs the 13" Macbook Air as a pro, but in fact even the previous MBP had a slightly smaller footprint than the 13" Air, this is even smaller though. The Air is in fact a pretty large 13" laptop in terms of footprint.
Best cheap laptop – Best budget laptops 2016 UK
To me the root problem for this alias proposal is that go currently ignores version dependencies.

Go is designed so that we have to assume that an API and the compiler are either perfectly backward compatible or immutable. This is a simplification inherited from C and other programming languages.

If we want to support changing an API, then we have to specify version along the package name and import statement. Some packages already do that but it isn't satisfying because it is hardcoded in the package name.

I like the versioning rule chosen by ICE from zeroc. A version is not backward compatible with other versions. A release must be backward compatible with previous release of the same version.

So it should be possible to specify a version and release for packages in import statements which specify that the specified release and all subsequent release are valid.

Dub, for the D programming language is going that line of direction.

I'm aware that it may create a dependency hell. But it already exist and is hidden. The alias hack is not a good solution. It will make things worse by making the rules more lax.
> there is a streak of anti-emotion dogma in rationally oriented communities.

This is certainly true.

I feel you're responding more to this perceived anti-emotional bias than to the actual content of Crocker's rules.
Also the repeated use of "break down in mid-flight" irritates me. To me it reads too much like "break up in mid-flight", as in, the plane breaks into small pieces.
Walking is not often from-A-to-B traffic. Walking is part of human behaviour, a way to immerse and express with regard to themselves and their surroundings. Similarly to how humans pause to think while they're speaking―or writing, as I am now―they also tend to pause to wonder while they're walking. Humans aren't robots and a sidewalk, a cafe, or a department store are good places to exhibit this natural behaviour. That should not come as a surprise to anyone and people who need to rush fast through will simply dodge any such obstacles. And people blocking entryways get soon nudged to the side by the stream of people.

It's not much different from that when a human is driving. The conditions do dictate some limits to how the driver can wander about (you can only mostly go straight on a highway) but everyone will stop to think something at times and maybe happens to slow down or slowly steer left/right until they refocus on driving again.

However, on the road, this behaviour is very irritating for those who are in their from-A-to-B mode because, unlike in a busy railway station where they can just snake through the crowd, with the worst case of gently bumping into bypassers while at that, they can not easily go around the slower drivers in busy traffic. Driving is basically monotonic robot work, or should be. It's not a natural way of being that lends to distracted behaviour as walking about does.
The problem with all green thread implementations that I know of is that they're language and/or framework-specific. So the moment you start using them, you get the same set of problems as using setjmp/longjmp in C across the boundaries of foreign code - it either just blows up spectacularly, or at the very least violates invariants because the interleaving code is not aware that someone's pulling the rug from under it.

This can only be solved by standardizing a fiber API and (per platform) ABI, and by forcing all libraries in the ecosystem to be aware of fibers if their behavior differs with threads in any way (e.g. if TLS and FLS are distinct).

Callbacks (and hence promises), on the other hand, work with what we already have, and are trivially passed across component boundaries as a simple function pointer + context pointer, or some suitable equivalent expressible in C FFI. For example, I can take an asynchronous WinRT API (which returns a future-like COM object), and wrap it in a Python library that returns awaitable futures; with neither WinRT being aware of the specifics of Python async, nor with Python aware of how WinRT callbacks are implemented under the hood. On the other hand, if WinRT used Win32 fibers for asynchrony, Python would have to be aware of them as well.
Well, you probably don't want it continually open, because then you can't use it for authentication?

If you did want it public, you could probably set up an ifttt recipe to post them all somewhere?

Oh, alternate idea: set up a thing to forward all the emails to e.g. a tumblr "email to post" address?

Something like that.

Edit: wait I think ifttt calls them "applets" now instead of recipes?
> I'm not a trump supporter (not even a US citizen)

Me too!

With Hillary I think American foreign policy will definitely be a continuation (she was the person in charge of it for 4 years), and that's not such a good thing for the rest of the world.

At least with Trump there is the possibility that things could change. I also quite like his ideas around addressing corruption in politics, though again as you mentioned, whether or not he'd be able to actually do anything about it if elected is a different matter entirely.
I get the impression from the review that the reviewer is reporting his experience with using the MacBook under real-world conditions. He's not performing benchmarks. Whether or not there's a performance improvement wouldn't really need to be included in that, would it? Indeed, he specifically mentions that he didn't have the opportunity to perform speed tests:

"Being on the road, I haven’t been able to do methodical speed or battery tests, but I can say that the battery life on this laptop seems to be a lot more than on the MacBook Air. It also handled some more intense work—editing multi-track audio in Logic Pro and removing noise from audio with iZotope RX 5—with aplomb. Some of that may be the result of the faster SSD in this model, but some of it is at least the responsibility of the processor."

Do you get the impression that he's trying to hide something? Do you have other criticisms besides this point?
> there was not a single fatality

This strikes me as the same reasoning that Feynman criticized in the Rogers report:

> The argument that the same risk was flown before without failure is often accepted as an argument for the safety of accepting it again. Because of this, obvious weaknesses are accepted again and again, sometimes without a sufficiently serious attempt to remedy them, or to delay a flight because of their continued presence. [1]

Just because no one died doesn't mean that the practice is safe. It might be safe, just like it could have been with the shuttle, if the engineers had designed the o-rings to withstand erosion. In that case you'd have tests and a spec for how much erosion is safe.

Similarly, unless there's a guideline on acceptable rate of mechanical failures (which the article suggests there isn't) "there was not a single fatality" is not an acceptable proof of safety.

[1]: http://science.ksc.nasa.gov/shuttle/missions/51-l/docs/roger...
You can uncheck Plays.tv/Raptr/AMD Gaming Evolved during the installation or uninstall it after the fact. It's seperate from the drivers.
Well, Perl 6 throws defined exceptions by default for most stuff like this, and would be very explicit as to why it couldn't open a file. Tests are part of the IO stuff too, to see if it exists beforehand if you like, or check permissions. Also, if you like you can do all the steps of using a normal file open and iterate over each line and split the words yourself if you want to. Your choice. ;)
> It's like that everywhere in Europe. Nobody says 'see you at fifteen'.

Sorry but that is not how it works in Portugal.

We usually say 15.00 unless it is clear from context that 3 is 15.00.

For example if I am scheduling to meet for a coffee at 3, it surely isn't 3 AM.

Now if I am talking about meeting for something else at 10, and it isn't clear from context, usually I will be asked if I mean 10 or 22.

Besides AM / PM is something that we have to deal with in English based devices, that is it.
From the start Toshiba have had a vision that laptops will replace desktops. They were also first to market.

http://articles.latimes.com/1989-11-07/business/fi-1099_1_co...

I have fond memories of the Toshiba Satellite Pro models that had the battery charger built into the laptop. The power cord was the same figure eight lead that you could find powering radios and other home electricals. If you worked in server rooms, meeting rooms, your own desk, at home or in the field, the lack of power brick was a huge bonus.

The desktop models 'failed' but look how advanced some of them were:

https://www.toshiba.co.jp/about/press/1996_09/pr1101.htm

Here you get a remote control and a home media centre that I wouldn't mind having today!!! It is like a desktop version of what a mobile phone offers, functionality wise.

Another Toshiba special were the Portege tablets that they brought out before iOS/Android tablets redefined what a tablet computer was. One had to pretend that the pen input was viable, pen to text was theoretically possible but not what you would use. Superb engineering including a 12" 1400x1050 screen and their own HDD.

Another retro Japan favourite is the Canon BN22. This was a laptop with a printer built in. There were models of laptop + printer than what made it to the UK market, the first one failed to find a niche in the UK and there were none coming to the UK after that, in Japan the concept was updated with the times into the Windows 95 era. I can remember seeing a Canon BN22 and being genuinely awed. It had the same form factor of laptops of the era, i.e. ungainly with the keyboard at the front. The space at the back had a printer sneaked in and the paper path went from the front to the back of the machine. Looking back the dimensions of this machine were a bit nearer what you would expect for a printer rather than a laptop.
Some companies MitM the traffic (installing their cert on all computers) so there's that.
There are a lot of them.

i.e. https://www.gnu.org/software/social/
That blog post explains the costs but not the revenues. How are they funded?
> Assange has claimed multiple times, that he thinks these elections are a farce... Perhaps he knows some things you and me don't.

I imagine Russian intelligence knows lots of things you and me don't, yes.
Flagged, then dead, and now back up. -- Edit: and now flagged again. --

Someone wants it down, and someone wants it back up.
> We can have that discussion without crying racist.

I hope so, but threads like these are depressing.

It's a good thing to point out that argument <x> is often used as veiled racism, or to explain how the underlying dynamic might be more racist than we might be aware of. But what I'm seeing here is false equivalence: "because racists say <x>, <x> is a racist argument merely by association. or too close for comfort to be able to discuss at all." This shuts down any conversation and the person holding view <x> walks away feeling misjudged and quite likely still holding view <x> because we humans have trouble separating a good argument from any judgment that comes with it.

I would very much like it if we could avoid that here, even if we know for a fact that the person bringing forward argument <x> is an actual racist.
If you talk in the time scales of millions of years, yes. Otherwise it is not true. Global warming has the potential to eradicate most marine life as we know it. And once it is gone, it is gone for all the time scales relevant for humanity. And we do not know how far the ecological impact would be. Just killing the coral reefs would be a tragedy, but if we are unlucky, this triggers enough eco systems to collapse that also our direct survival is endangered.
I'm curious, why don't you run findbugs directly rather than (I presume) paying Coverity?
Yes, the ones where you pay with your content.
Sorry, I wasn't clear enough. I wasn't asking about selling the thing. Just building it.
EDIT: Since it's been too long bbswitch = Bumblebee (which NVIDIA actually helps also) the open source implementation of prime, both of which also support the older Optimus laptops but ymmv with BB.

Also it looks like PRIME supports synchronization now if you have a distro with DRM support (no not the bad kind ;) https://devtalk.nvidia.com/default/topic/957814/prime-and-pr... so if you are using their currently suggested setup you don't need to switch manually anymore.
I think the first thing to dump is the daylight savings time concept.

Then rebase the timezones based on UTC.

It won't help when you have a polar winter or a midnight summer - but at least it will remove unnecessary conversions.
Just this morning on my bicycle ride to work, I was nearly run down by a taxi making a blind entry into a large road and doored by a 10-year-old. The fear of cars is not "old school" but very much real. This is not to mention the aggression that drivers go and build up in their small bubbles. I am always prepared to get off my bike and take them up on their threatening offers. I look forward to less aggressive, more responsive computer-controlled vehicles.
International fixed calendar
Serious mistakes committed by Drupal developers
Cybathlon 2016: No cyborgs yet, but we're getting there
GeForce Experience is a seperate application that automatically updates the drivers for you. ShadowPlay is their hardware accelerated video capture software. They are optional.
Self-Control Is Way More Important Than IQ (2009)
Elm: The Gateway Drug to Functional Programming
What would happen if we did this, is that all the different timezones will now have an unofficial "sunrise" time, that is the time where you get into work/school.

Sure planning is "easier", except now you have to check that it does not interfer with every participants "sunrise" time. And if planning seems to be that hard, we can keep the current system and plan after UTC.
The distinction I was trying to make was one between where in the toolchain it lives: error-prone is part of compilation, whereas Findbugs is after-the-fact.

Error-prone is a compiler plugin _mechanism_ - once you have an error-prone compiler, the checks are arguments to the compiler just like APT annotation processors are.

It's built on a standard API - the JavaCompiler mechanism built into the Java SDK - but yes, the code does have further dependencies on com.sun packages. This is a little confusing because why expose the compiler for invocation and extension when extensions have to rely on unsupported code?

So, yes, there are ways where the distinction is important, but they're orthogonal to the point I was trying to make.
Quick fix for an early Internet problem lives on a quarter-century later (2015)
I've tried to read Utopia but that book is written so dreadfully I had to drop it after 20 pages or so.
We can't even manage to agree to get rid of the nearly pointless and _highly_ disruptive leap second...
Hence why Google is happily replacing every GPL component left in Android with MIT BSD ones in each Android release, GCC has already been shown the door.

In Fuchsia, they are even replacing Linux by their own micro-kernel, BSD licensed.

How much contributions has Sony given back to BSD from their PS4 BSD distribution?
Signed up, Not yet received activation email!
I'm a big fan of the 'look twice, save a life concept' but motorcyclists can be more adequately described as suicidal than the typical driver can be described homicidal.

I've been in a few situations where I had to work very hard to not kill/injure someone because a motor cyclist was being completely reckless. It is super annoying to have motorcyclist squeeze around you on both sides on a one lane ramp merging info traffic. Or a motorcycle sitting in my blind spot without even the decency to stay near the center of the lane.

Its not really different from any other driver, except the complete absurdity of driving among cars at car speed with literally no safety mechanism beside plastic wrapping your head should demand a heightened level of defensive driving.
The shifting tone of the sequels put a lot of people off, but I regard the original five books as some of the finest I've ever read.

I can't tell whether you'd like them, but I do wish you luck.
New MacBook Pro Taken Apart by iFixit
Cause #0: implicit information.

Implicit information may force people to guess what is being said. Turns a simple thing into a riddle.

Cause #-1: lack of consistency

When something is designed in a different way, people try to infer why it's different. If they turn out to be the same thing, it pisses people off.
Public Service Announcement:

https://qntm.org/abolish

(So you want to abolish Time Zones...)