skysight-inc/HackerNews huggingface dataset:
> Lock safe methodologies can prevent the crash, and if designed specifically for the data in question and the data structure supports it, can possibly ensure no corruption.

Which was the entire point of my post. "Thread-safe" does not guarantee "usage-safe", and using them interchangeably is a fallacy. If the synchronized StringBuffer does not provide the guarantees you need anyway, there's no point in paying the cost of using it.

> Given with strings you probably have data corruption no matter what, do you want crashes on top of that or not?

I just said that, yes, I would rather the program crash than silently corrupt data. I would rather it crash 100% of the time, but I'll take intermittent crashes instead. A crashed process can be restarted; it's very much harder to fix data once corruption hits. And if data corruption hits anyway, at least if I also have a crash I have an idea of where to look for the issue.
You can't disprove a null, just fail to reject the null. Failing to find the Higgs would not have provided evidence that the Higgs did not exist.
I've read about it before, at https://en.wikivoyage.org/wiki/Avoiding_travel_through_the_U...

Basically, the problem seems to be that the USA does not have "sterile transit"; if your plane stops there in the way to somewhere else, you have to disembark and go through customs, and you need an expensive visa.
Yes. Power Pivot is the reason that I said Tabular arguably came to SQL Server 2008R2, which can run Analysis Services in a mode to support a Power Pivot workbook hosted on SharePoint. There was no standalone SSAS Tabular, but the Vertipaq engine and DAX were run on a SQL Server instance.

Power BI Desktop (and hosted data models on the PowerBI.com cloud service) is also powered by the Tabular engine and utilizes DAX as a query and modeling language.

Microsoft is pushing Tabular hard. It's probably the right choice for most organizations, and at worst serves as a great prototyping tool for a Multidimensional model (when we have clients who need Multidimensional for whatever reason, we often still do initial development and pilots on Tabular).
> I actually think that dynamic languages have negative efficiency impact over long periods of time and large numbers of developers.

I agree, but that does leave open the possibility of them being more efficient in some circumstances.

> I could also "catch" crashes with techniques such as watch-dog processes with very similar effects.

Without a system for handling the crash information in such a way that you can feed it back into the restarted program to retrieve prior that and recover from it, I don't really see how they are equivalent.

> Now if you really mean "crashes" as "program faults due to memory corruption", as opposed to "unexpectedly halting execution", then you're both using a niche definition and gave a bit of deceiving definition of "unsafe"

I mean either, for the entire program, not some executing branch. I think "crash" is fairly unambiguously accepted as "an unrecoverable problem within the current running context causing it to halt." An exception is not a crash, it's a problem, which if unhandled can lead to a crash. Perhaps I'm in the minority in my opinion on this, but I don't think so.
I can't really escape a feeling which tells me that apple wants to get rid of OSX completely. Ever since I posited the possibility a few years ago, they have followed my estimated trajectory almost perfectly, only a little slower. Bringing more and more iOS into OSX, even where it doesn't _really_ fit. The dual use file system lockdown (etc) feigning increased security as it's sole motive, but in reality it's as much about pushing all code within a set of API's shared between iOS and OSX.

I admit it sounds a bit like crazy talk, I guess we'll find out in a couple years.
It can be done through Mondrian OLAP. See mondrian-rest [0] for an example implementation.

[0] https://github.com/jazzido/mondrian-rest-demo
Coincidentally, Super Mario is a single player game.
They're actually violating the terms of their payment processor by doing so, but some small shops don't care.
Do you have a source for this? Are you talking about pthread_mutex_lock() ? Maybe I'm misreading you, but it sounds like you are saying it would be safe to treat a mutex as unconditionally unlocked inside a signal handler, which doesn't make much sense (what if a signal is delivered between _lock() and _unlock()? )
Again. Read the FAQ. It is there. The site has numerous points where they tell you to read it and the guidelines. Your lack of attention is a poor excuse.
That's a pretty bad privacy breach.
Actually single-level store concept was introduced in Atlas, used in MULTICS, AS/400. [1]
Some modern and quite high-performance solutions are using this concept, e.g. LMDB [2]

[1] https://en.wikipedia.org/wiki/Single-level_store
[2] https://symas.com/getting-down-and-dirty-with-lmdb-qa-with-s...
The problem isn't the number of modifiers, the problem is that Apple uses symbols for them in the UI that over time it has progressively removed from keyboards, and which have no obvious connection to the names on the keyboards (except for Ctrl sometimes getting the same ^ treatment on other platforms, this just isn't the case outside of Apple.)
A ready-made platform is offered by Visionect - their dev kits for system integrators: https://www.visionect.com/development_kits . Meant for professional use and thus the price.

It works by using the display purely as a framebuffer, everything is rendered on server and sent over wifi/3g. It gets you amazing autonomy times and is easily powered by solar in outdoor installations.

disclaimer: founders are friends
I found forcing user to SMB weird given how crap their driver is...
The goal of this library is to provide the familiar sockets interface over a non-traditional eth, in this case sound.

Can you expand on your question? I think I understand what you're saying but I don't quite see what it would accomplish.

And this is an "actual" modem, whatever that means. If you mean an IETF/RFC modem spec, there are many reasons. Those specs are focused on narrowband POTS limitations, which we don't face over a less-restricted channel. Implementing those features might be interesting from a vintage perspective but would require substantial work to achieve compatibility for relatively little gain.
Thinking outside of the box with NGINX series – split_clients command
Apple Might Have Just Made Siri into Something Really Good
> I am hoping I can still get a "dumb" panel the next time I need a new TV (which is hopefully never).

Protip: when you go to buy one, don't go to consumer electronic retailers - if you find a commercial electronic wholesaler (e.g. one that sells equipment for businesses), you'll find heaps of dumb TVs that are basically giant computer monitors. Same panels, better warranty, and nothing in them except a panel and a bunch of input ports.

Businesses often use these in reception areas, operations rooms, etc.
Listen, I work for a giant manufacturer, I know what drop shipping is. You've given another example of drop shipping, the first being manufacturer directly to retail, without using a distributor. In the end, drop shipping is about cutting out the middle man (distributor, or in your case the retailer).
Backend developer.

Main side project is Tablesaw, a dataframe for "large" data (100M to 1B rows) in Java (https://github.com/lwhite1/tablesaw). Although, it might be better described as a personal, in-memory, column-oriented, data warehouse. :)
How is object recognition possible on a (i)phone without a huge/massive dataset like Google uses on Google Photos' AI backend? It has to be worse AI than from Google Photos. Can someone clarify?
Where the Hell Are the New MacBooks?
Except for local storage the information in this post is useless and partially false.
After reading your message, it just clicked to me that the option symbol could be a fork in the road.
It does not. It is the difference between an exploit that yields a root password and one that yields a shell at uid=0.

HttpOnly is almost totally cosmetic.
Diversity leads to greater business performance, more creativity and innovation [pdf]
Also all valid:

surely.trim.organ stuff.small.organ tickle.long.organ milk.long.organ milk.needy.organ

glorified.body.openings

stiff.little.finger stiff.large.organ

take.fine.compost

wrong.wrong.wrong
As a huge haskell fan, I'd love to hear more of this story. There aren't enough good writeups of companies trying haskell and it not working.
If you did it as a traditional modem then one could hook up any old piece of software to the appropriate character devices and you'd be off to the races. Not everything is sockets, and there are simple and relatively easy to use wrappers around a standardized serial character interface to turn such a connection into one supporting all of the regular internet protocols. It seems - but I may be wrong about this - that this solved something at a different layer than what I would have expected.
As others have said, there's peril to be had there for sure, so tread carefully. Minimize the scope of your handler is the best advice, certainly also refer to "Async-signal-safe functions" in signal(7) if you must use libc funcs.

One challenge in a distributed system when there's (ab)use of signals is finding out which process issued a signal. There might be a better facility to do it now but I've used systemtap [1] to find out who the sender was with satisfactory results.

[1] https://sourceware.org/systemtap/examples/process/sig_by_pid...
Well, then you haven't been using macs for a decade, but for a year, times ten (and that's totally fine, unless you're leaving arrogant comments on HN about "why we tolerate this or that"). I've been using macs for about 5 years and I still learn new useful features and shortcuts, and having 3 modifier keys is so useful (e.g. emacs + iterm2 + spectacle) that I can't see myself going back to linux/similar. ETA: also, brew is lovely for people who want a stupid simple package manager
I'm not going to claim that "current" electronic voting machines are good, but the article makes no convincing arguments beyond an "I am a computer scientist" appeal to authority that it "couldn't" work. Honestly if you are going to talk about the problems involved in voting at least discuss some of the interesting anonymity preserving and deniable cryptographic techniques people have come up with- ring signatures, blockchain verification, etc. Maybe he's just assuming the powers that be would never let an actual trustless system get into play. If I can manage and view my money trustlessly with, e.g., bitcoin (and verify all transactions back to the original block) then there is no reason I shouldn't be able to do the same for votes - and verify all votes back to the original block.
Althea Mesh sounds like a great idea.
Properly, in this context, simply means tax it like you tax fuel/energy for other modes of transportation.

Airlines have been very successful at getting special treatment by scaremongering "no more connections for you". Which is certainly a mostly empty threat, because connections will only go down by as much as demand elasticity reacts to the price difference.
NSF Funds 'Wearable Doctor'
Google I/O does.
I'm guessing you aren't in Missouri, then? :)
Ooh $350k, about what it costs them to hire one software engineer for a year
Cool! Thanks.

I had heard of Mondrian, but didn't think to check from that end if it could use MonetDB as a back end.
This really got to me and it took me a while to realize what is going on (wrong height of my desk relative to the chair so my lower arm is at an angle to edge of the desk). Very bad and it apparently takes a while for things to get back to normal (it only took 48 hours to mess is up!).
He's in SF w/ Casey and Marco... :/
It's worth pointing out that Concorde didn't cruise using its afterburners; it only lit them briefly to punch through the transonic flight regime.
this one works, thanks!
Right, but we are talking about a communication platform which inherently should be crossplatform
The answer is definitely: How did you train it? If you trained it by showing it tons of movies and television, then you'd get a modern foley artist in a box, right? If you want them to do something else, you'd need to get a bunch of stock footage with stock audio. Both are doable, but which was done here?
So is Amazon happy that one of the most important partners of their business suffered ? Cant we trust UPS and Amazon more than FAA in this case?
This is for the use case of: "Something weird happened on my account, so I check sessions and see that someone used my account from across the country. So I log out other sessions."
I always thought a large cipher blockchain would be a pretty good idea. One could argue that "analogue" voting also has many vulnerabilities in the voting stack.
Monique, the hen who is sailing around the world
I have worked with Meta in the past. They are not going to release a viable consumer product. I have serious doubts about Magic Leap achieving anything of the like either.

AR is a good idea, but the management over at Meta has about as much chance of making it viable for any customer as uBeam has of delivering on wireless charging.
though not sci-fi, but check out hiyao miyazaki's anime, really well done and he has this way of never portraying characters as bad, everyone is good, very consistent across all his movies, princess mononoke, porco rosso, my neighbor totoro, etc
I've had F2FS on an Android tablet for many years. Resurrected it. However I'm running Debian on my laptop and I'm scared to try f2fs on
/ Because i get warnings about it being not fully supported "yet" i would love to have an SSD optimized FS on Linux. Since AAPL will open source the release version, is it conceivable that AFS could replace ext4 as the default Linux FS?
Difference was how Steve sold it vs the two presenting iMessage today
> No longer developed because ... pm-utils were basically done bar some odd hardware quirk or other ... ?

I doubt it's this one. There's one or two messages to the mailing list each month or two month about a bug in some chipset or another.

> I can't shake the impression that user space devs are deathly afraid of their project going "maintenance", and thus either abandon it or depreciate it for a new take on the same problem space (that in turn gets to the same point etc etc etc).

Or perhaps it was an underserved portion of the ecosystem, and the people maintaining it left, or decided they wanted in on what systemd was doing, and as project eventually (5+ years later!) swicth away from it to the next (only?) thing which should get new features, being actively developed, that just happens to include systemd. You can either see that as "systemd is eating everything" or "systemd filled a need, and projects had been waiting for that". Whichever one is more true probably requires a deeper look into the details, but that people assumed it was the former (IMO because of mob mentality, not because of any careful thought on the details), that's the story that survives unless someone spends some effort to refute it.
YNGNI: /'iŋ-ni:/

The word you're looking for is inpronunciable, and it's not exactly as though "YAGNI" is some shining example of pronunciation to begin with.
The table looked very awkward. I actually previously had a solid wood IKEA table with two folding leaves and storage space in between, which cost about £200, and looked a lot more usable (and attractive) than that table. Admittedly you could only get 6 people round it rather than 8/10. But then again, it didn't cost £3000.
The atmosphere has hit a grim milestone
I think it's a strategy by "those in power" to tightly control who gets hired. They make the application process so bad that people with options opt out of applying.
Telegram team always say they are too secure, it is interesting that they have such a critical bug
Ah, yeah, that makes sense. My plans for this library are mostly focused on using the sockets directly, with the library linked by both peers. I'm really interested in being able to use this as a simple UDP client/server.
It's not even a preference thing though. Android phones are absolutely killing the low-end smartphone market and international users are very heavily Android locked-in. I can buy a pretty solid Android phone for 200-300 dollars, even less these days. The cheapest iPhones are 400-500 dollars. It's why Android dominates iOS globally.(https://www.idc.com/prodserv/smartphone-os-market-share.jsp). Outside of SV, Android is still the most common mobile OS (including in the US).
(raw) flash and spinning rust are fundamentally different, because spinning rust drives provide a READ SECTOR and WRITE SECTOR primitive, while raw flash provides READ SECTOR, ERASE (large) BLOCK, WRITE (small) SECTOR primitives. Stuff like UBIFS do try to move the wear leveling code into the OS. But the big players like Windows' NTFS and Mac's HFS were originally designed for the spinning rust primitive, so I guess vendors of flash storage (SSD drives, USB sticks etc) had to deal with providing a translation layer to emulate the spinning rust primitives on top of the nand flash primitives. I'm sure various nand flash vendors have different characteristics / spare blocks / secret sauce / defects that are masked by proprietary firmware, and probably see a significant business advantage on keeping those secret. Even things like building smarts about how a FAT filesystem is likely to have heavy rewrites of the file allocation table compared to file contents, into the firmware for USB sticks where FAT is a likely fs, could prove an advantage. So being a single vendor behind the entire stack from the raw NAND flash memory to the motherboard it's soldered onto to the OS is likely very advantageous.
OK, now this is turning into a real tangent on exceptions vs crashes. I see little difference between an exception with no actionable programmatic resolution and a program crash. You can always retry, but the bottom line is that there's never going to be a good answer to flooring a banana. You can try to floor something else, or you can try to do an operation that's not flooring, but that particular combination isn't going to ever have a good solution.

> I mean either, for the entire program, not some executing branch.

That's a pretty arbitrary line to draw. The difference between one thread acting as a watch-dog for another thread, or the same situation with processes could probably be made indistinguishable with the proper setup.
> The reason why The DAO tokens are cheaper than 1.0 ether is because of this uncertainty.

That's a wrong way to look at it. The price of a DAO will equal to 1 ether minus the costs of shorting 1 ether.
Paul Hegarty is such a fantastic instructor of that class... its is hands-down THE resource to get started with iOS dev.
This is a popular undergrad course at Berkeley. To be clear, it's mostly focused on GOFAI (good old fashioned AI) - things like tree/graph search, constraint satisfaction, logic, some basic graphical models, and a bit of RL/ML at the end. It's useful to know about (because these things sometimes show up as components of ML systems), but also fairly disjoint from the core machine learning field that people are undoubtedly interested in.
GMSK [1] among others. Pretty cool!

[1] https://en.wikipedia.org/wiki/Minimum-shift_keying#Gaussian_...
Or perhaps concern with having to deal with 3rd party iMessage/Facetime clients while at the same time trying to maintain a high level of security. Apple doesn’t want anything to tarnish the security reputation of these products.
There was some allegations from Kansas statistician Elizabeth Clarkson on voting anomalies.
Some new features to Apple's platforms that didn't make the keynote
Do you think Apple will release it with GPL-compatible license?
Haven't used JWTs myself, but whenever I read an article or tutorial about them, it's always in the context of replacing session cookies.
This is absolutely the case. Having been through my share of re-orgs due to M&As, another side-effect is that often some of the best talent leaves when things don't go quite the way they wanted.
You're choosing a suboptimal attack spot in your paper voting attack scenario. Instead of manipulating the thousands of people around the country who count & send out the results of those booths, it's easier to manipulate the far fewer people who do the aggregation for final results.

Also a computer voting system that is exploitable via "one hack" is inexcusably badly designed. Yes hacks happen & adversaries have zero-days, but it's possible to build a computer voting system that is highly resistant to those scenarios. As a very simple example: have a standardized vote format that will be counted by three independently implemented systems, each on a different OS, running in parallel. A great system will go to far greater lengths for protection, but this should already show that a simple "one hack" wouldn't work.
If you've ever read the Lions' Book commentary on 6th Edition Unix, you'll notice that many parts of the API as implemented back there are pretty solid -- quality, well designed interfaces that have stood the test of time.

Signals are not one of those parts. The 6th Ed signal handling code reads to me as somewhat of an afterthought whose use cases were mostly "kill the process for a fatal signal or terminal ^C", "ptrace for a debugger" and maybe SIGALRM. The data structures don't allow a process to have more than one pending signal -- if a new one comes along the fact an old one was pending is simply dropped. Running a signal handler automatically deregistered it, leaving a race condition if two signals arrived in close succession (this is a well known bug fixed by BSD later). And EINTR is an irrelevance if signals are generally fatal but its effects spread like poison through every other kernel API if you need your program to be reliable even with signals being delivered.

The worst bugs and races were fixed up by the BSD folks and others, but the underlying concept is an unfortunate combination of "basically irredeemable", "indispensable" (you have to have some kind of "kernel tells you something has happened" API, and signals are what we got) and "insidious" (thanks to EINTR). I think they're a strong candidate for "worst design decision in unix".

(PS: one of the reasons they stand out in 6th Ed is that so much of the rest of that code is so good!)
Why would they?

Stripe is just one of X layers which Apple Pay can run on. There's no need for them to get into that business.

The next stage for Apple Pay is to run their own payment network between Apple Pay users. No Stripe required, Apple takes a processing fee instead of First Data, etc.
More than that. A salt for each "session".

Each JWT contains two pieces of info: user ID, and salt. This stops the JWT from being a deterministic token that is always the same each time a token is generated for a specific user.

It also allows invalidation. On each request a middleware checks validity of the salt from the JWT. A Redis cache layer here makes this a 1-2ms operation and easy to scale. If you need to invalidate a JWT delete a salt and the respective token is now invalid. Or delete all salts for a user to invalidate all their sessions.

Honestly this use of a JWT is basically just a lightweight session that passes the session ID via a technique that isn't insecure by default like cookies are. Rather than having to opt in to CSRF protection your stuff is hard to CSRF unless your application persists the token insecurely.
You'd get that just about for free by running SLIP or PPP over your audio modem.
Are you sure there's no way? Or do you mean that's not economically sensible to do so?

RTGs are designed to survive uncontrolled reentry. I am aware that they are much simpler devices, but we are talking about containment.

There's no way to get the public to accept that though.