skysight-inc/HackerNews huggingface dataset:
It would probably have been FutureSplash Animator, which became Macromedia Flash and then Adobe Flash. For a long time Flash was the de-facto web scripting language.
>Lisp's one big selling point is macros.

Maybe not quite as big of a selling point, but lisp has also always been the best environment for writing programs that need to modify themselves at runtime. Homoiconicity removes the limitation that code must be known and constructed at compile-time.
?? I don’t understand what you mean. Those other languages don’t have pointers, they only have references, but what do they have to do with this?

Why do you still think there’s some yes in C? It’s not making sense yet that your memory is gone after you return? Returning a pointer to a local variable is exactly the same as calling delete or free on a pointer and then reading from it. You officially don’t own the memory after a return statement, so if you try to use it, then what happens is indeterminate. Again, since it doesn’t seem to be sinking in: it is always wrong to return a pointer to local memory. But, if you really really don’t want to listen, and you’re sure it works sometimes, then I say go for it!
Are they though? Last I checked that describes Apple's App store not Android
This is a solved problem.

Our grocery store (Wegmans) has labelmaker scales in the produce department, and the four or five digit code right next to the produce items. You bag it, weigh it, and label it yourself.

Speeds up the human checkouts, too.
Manipulating/aggregating metrics is a giant pain, you have to understand what exactly the implementors though `max` or whatever means and try to match it up to what you need.

One thing the article doesn’t address is that logs have to be accurate and metrics should be consistent, but not vice versa. If your performance metrics are always 10% out, they’re still perfectly usable (as long as they’re always 10% high or low) to alert on or to compare to metrics from a known-good historical period.
Exploring Perceptual Illusions in Deep Neural Networks
> I don't know how practical it is, but it would be nice to see a framework where security updates and feature updates were separate things. One could keep one's site secure through updates without having to debug formerly working things every few months.

This is more or less what an LTS release is. The problem as I see it is that, as the codebases diverge, it becomes more and more work for the dev teams to support what is now essentially two different products. And especially in the open source world, it seems futile to expect unpaid or low-paid contributors to continue to do extra work simply because someone else's dev team doesn't want to put in the work doing updates.
That is a brilliant idea. I'm surprised I haven't heard/thought of that yet.
This African Union (AU?) is likely going to be quite friendly with China given Chinese investment in the area, so I doubt they'll be the ones to put pressure on China.
In this emotional response full of links, you forgot to articulate your point.
>money up front with cost later

If you're a thieving dictator, that's money up front with costs never.
Product innovation is not enough to beat a competitor’s network effects
Yeah, I'm a huge fan of erroring out properly. It makes it much easier to find problems before they cost money.

I think the erlang/elixir model of fail fast and try to restart is the best for availability.
I upvoted this comment and it went back to grey immediately, and I wonder how the people voting this comment down are want to explain themselves, what counter-arguments they care to offer and what their motivations are because the Facebook currency question and its relationship to economics in Africa are not mutually inflammatory topics of discussion--it absolutely needs to be talked about and highlighted.

https://www.bbc.com/news/world-africa-48882301
What It Takes to Build a Marketplace: The Poshmark Story
> Your credulous, at best, belief in law enforcement's use of the system largely ignores the prevailing example given in the article

Law enforcement will always be a compromise. There will always be some who abuse it, and there will always be a need for it (if you want a reasonable level of civilization anyway). It's not binary. It's not "Give up all freedom and rights for infinite security" vs "Give up absolutely nothing for absolute freedom" with nothing in between. The line has to be drawn, but it is arbitrary, and a lot of people have different opinions on where it should be drawn (rightly so! there's not an obvious place to draw it).

We certainly have to be careful not to draw it too far on one side, but that doesn't mean it has to be completely on the other side.

Eg: I personally think it's too far to put surveillance cameras everywhere, but I'd be ok with cameras and facial recognitions on some major roads (they already have pictures associated with driver's licenses and various other documents for acceptable reasons).

Yeah, it might get abused sometimes, but everything can be. Everyone for themselves and hope for the best hasn't historically worked out so hot either. Law enforcement being completely neutered with zero tools and powers isn't very effective.
> I'd write more but don't want to make this post overly long. There are several useful articles online on the different methodologies and approaches to achieve this.

Do you have some of these articles in mind?
A more generous interpretation is the Orange Orangutan has managed to capture the attention of the entire American nation on a 24 hour basis with his antics.
Right. So why the obsession with Russia? In this book?

https://en.wikipedia.org/wiki/The_Grand_Chessboard

Do you know who Zbigniew Brzezinski is?

You comment proves a total lack of any knowledge in geo politics.
"Here is linux on a hard drive microcontroller http://spritesmods.com/?art=hddhack&page=1 "

No, that isn't Linux on a HDD microtroller. It's bare metal on an HDD MCU sort of fooling the Linux box that is accessing it. True that you can run uCLinux on some MCU devices, but this thread isn't necessarily showing the best one for that. Dancing bears are amusing, but not common or recommended.
> Go authors stated multiple times that there are no plans for a Go 2 at the moment.

There are plans for Go 2[1], Russ Cox has written blog posts and given talks about design improvements for Go which would go into a Go 2. There isn't a roadmap (yet) but this discussion has been going on for the past year or so[2]. They talk a bit about next steps in the most recent blog post about Go 1.13[3].

[1]: https://github.com/golang/go/wiki/Go2
[2]: https://blog.golang.org/go2draft
[3]: https://blog.golang.org/go2-next-steps
Given that the blog post in question quotes from "On the Road to Fedora Workstation 31," I think Red Hat's adoption of Wayland is germane here.
Thanks for the reply - I hadn't actually thought in any depth about what's going on, and I'd like to get in GPU programming at some stage.

Also, sorry about the barely prompted and completely unjustified wall of rambling text - this is something that I really should've given more consideration to already.

That's a programming model that has the potential to go very wrong, very fast if you don't think in depth about what you're doing.
Branches with branches are going to be very problematic (with exponentially decaying throughput), although multiple branches at the same level are handled very cleanly.

To be honest, I don't know how I thought that it might be rescheduling things instead.

The sort of rescheduling that I seem to have been thinking of, could only make a difference in cases where the batch size exceeds the wave size, and my guess is that the factor of difference would need to be large to make an impact.

At the base case, NOPs and rescheduling would perform identical operations - so all the scheduler would get you is a hardware overhead (the time overhead could be mitigated when running on a single wave).

The scheduler would also introduce latency since different waves in the same batch would need to wait for each other before rescheduling could proceed.

You'd cause problems for your memory layout - programmers referencing values from threads that have branched would probably need to be treated as undefined behaviour.

You'd also need to introduce a stack, per thread, to keep track of the wave histories - allowing you to unsort and re-reschedule at the ends of branches.

All this to run parallel execution on what seems to be uncommonly large batch sizes (I believe AMD just dropped their wave size down from 64 to 32 - I don't know if this is because 32 is a Goldilocks batch size, or if it's simply to achieve better performance on Nvidia optimised applications).
Your assessment is incorrect. The NEIC releases two intensity maps very quickly (1) 'Did you feel it?' based on internet crowd sourcing reports And (2) 'Shake Map' from instrumental readings.
“extremely rare”. At some point is a pretty big number. If it’s one and a million and your doing a million transactions per day .. maybe that’s ok but as it becomes hourly or every minute is it still okay? I guess depends on how much time it takes to recover from the locking event...
It's an interesting position to suggest that nvidia which has no obligation to support you in any way shape or form is shoveling anything down your gullet by not supporting the standards you prefer.

You could vote with your wallet but there aren't enough Linux users to move anyone's needles as far as gpus.
We did some client work up until about 2 years ago with Backbone, too. We loved it. The entire team knew it very well and it got the job done. At least a few developers at the client would also be familiar with it every time, so it was a win win.
Apple was not a major corporation in 2000? (But it's true that would be post-Java.) Then neither was Sun. (Or maybe FigBug meant IBM which pushed Java heavily a few years later? They also pushed Smalltalk before, by the way.)
Yep. I was interested in the post as I've always felt Django is python software "done right". I stopped reading when they started complaining about python 3.

Python 3 has been out for over 10 years now. Did OP really think Django was going to use python 2 forever? Frankly that's a selfish outlook, and I'd go as far as saying it's a cancer of software development.

Backward compatibility needs to be a thing, but not forever. Things need to be deprecated eventually.
Hey, Alexa, What Are You Teaching Our Kids?
My grocery store has smart scales that let you print a barcode for produce that you can scan at the self checkout line. At the scale you can just search for the product by name (e.g. “apples” will suggest “honey crisp apples”).

There are definitely still issues if you need assistance. The ratio of self checkout lines to attendants is 8/1 when the store is busy.
That works until there's ~only self-checkouts, then it gets slow again.

There's a knack to using them, and unless you have a generous number of them (I know of only two local stores that do), you end up getting stuck while the single staff member assigned to the self-checkouts assists customers having issues.

Plus it's not unusual for a significant number of them to be out of order, not accepting credit cards, only accepting credit cards, or just being generally temperamental.
>Saudi Arabia an enemy too

Drop the "enemy" talk. If there are good reasons not to do business with Saudi Arabia you can state them and if there are good reasons not to do business with America you can state those as well. None of that is relevant to whether there are good reasons to not do business with China.
Vanilla PHP is your friend then. Don't use frameworks.
I can see good uses for that if you're programming a Mars rover.

On the other hand, you lose the concept of "known versions" with that, and I wouldn't want it anywhere near audited code.

And in most circumstances it suffices to stop and restart.
Unfortunately it's not practical because the test matrix explodes. They would have to develop and test every security update on every previous version which is quite costly, especially if the codebase has diverged.

The best strategy is probably what many large distros like Ubuntu have adopted: designate only a few long term support (LTS) versions, and commit to supporting only those versions.
>This will all change when loan repayments are due and China insists on no-forgiveness and asks for more control of the actual infrastructure...

Only they won't. When I was at Halliburton you could see the insidious brilliance of the Chinese strategy in Africa. Sure, there is support for rail everywhere. Support for roads everywhere. Factories everywhere. Resource extraction. Etc.

But ask yourself this, where does it all go? Follow the map of their rails and roads and you'll see that a lot of them just go to ports. I mean, you can't even complain about it, because, of course, where else would it go?

But I have a final question for you, will Africans own the freighters?

My boss at Halliburton was a brilliant strategic thinker. Was basically 100% sure that by 2100 there'd be so much freight traffic that you'd be able to walk from East African ports, to Shanghai, via the Indian Ocean, without getting your feet wet.

So the Chinese are effectively giving the Africans loans and whatnot in name only. Really it's a trap. Only the trap is not monetary, it's a physical logistics trap. They don't care if you pay for the roads or not, they only care that the roads go to the port. That's the evil of it, if the roads go to the port, you've probably already paid for them.
but then it might be expensive to encode every possible dimension in the log stream
Do you know how 1024 people stand on 10 issues?
To be fair, it's almost impossible to build anything out of fully discrete components these days. If you use a TO series transistor, you could argue those are also ICs and vacuum tubes/relays aren't cheap or too easily accessible.
I think complexity here is migration to Python 3. Seems like the author picked Django and Python 2 in 2011. Python 3 was released in 2008. So by 2011 should have been clear that you might be facing a migration project sometime in future. Having made that choice getting 8 years out of Py 2 is pretty good. (Not saying he made the wrong choice. Would have made the same choice myself.)
Just cut it yourself.
Most distros have a nvidia driver package that aligns with the kernel version shipped. This also means updating one updates the other automatically.

Furthermore lag time for supporting newest kernel normally lags what 30 days?

In brief what you are describing is self inflicted wounds.
I'd be more worried about China - https://www.google.com/search?q=china+buying+africa.

I think that Facebook's less of a threat than it would like to be.
It was on the front page of NYT's International section when it was announced three months ago.

https://www.nytimes.com/2018/03/21/world/africa/trade-nigeri...
The alternate suggestion would work like EGLStreams. The current Nvidia driver can’t handle any more.

EGLStreams works by having children pass ownership of the surface they want to display to their parent for compositing. This invalidates said surface.

GBM is a coherent model. Handles are passed around to prevent the need for copying, but ownership isn’t transferred.

Nvidia’s driver is a black box, but I don’t think they can do things that way without some significant driver refactoring. Obviously that’s costly, so they’re trying to avoid doing it.

AMD took a gamble when they began their open source initiative. It’s starting to pay off now with stuff like Stadia and the Valve stuff. I feel like Nvidia is going to have to do an open driver eventually. I hope they’ve got at least something in the works that we don’t know about.

I’m not going to suggest replacing Nvidia cards if they’re working fine for what you do. Just look at AMD (or Intel next year) if you start hunting for your next card. Don’t fall into the brand loyalty pit.
Produce at self checkout takes max 5-10 seconds per item once you know what you are doing
Well, they sold out instantly! Good for AMD. I'll be excited if I have the opportunity to build a workstation using a 3900X. That's such a sweet spot for a 12 core to price for media work. Unless someone buys me a Mac Pro, I'll probably be crawling back to Windows / AMD with this release now that they have motherboards with TB3 and 10GbE on them.
Griesemer, one of the three original Golang developers, did his dissertation on extending Oberon to, I think, massively parallel computers. Golang has a bunch of constructs that weren't in Plan 9 C; some of the syntactic sugar comes arguably from Oberon, but most of the semantics come from Newsqueak and Alef.
Malaysian Prime Minister Mahathir denounced murder charges made by the JIT, saying "From the very beginning it became a political issue on how to accuse Russia of wrongdoing"

Also Ukraine as a suspect was involved in the investigation, while Russia rejected and evidence sent including radar data.

A circus really.
I have been using Clojure(+Script) full-time for 6 or so years. I hope I never have to use a less elegant or more verbose language. The trick/tradeoff is to work at early stage startups that leave you with enough control to choose your tech stack. If I did have to go back to, say... JS (which thankfully has improved in the past several years), I will at least bring with me a fresh clarity; Clojure certainly made me a better programmer.
I was 9 for 9, then I got asked to select a "palace". I didn't really know how to visualize one, but there was a picture reminiscent of a an clearly very ornate chair in a room, which I figured could be a palace interior. I broke my streak choosing that chair :(
This is the problem with technology. In the old days the police were required to use detective work to solve crimes with supporting evidence. Nowadays they use brute force technology to find an alleged felon then use brute force techniques to take them down. Usually the latter is based on probabilities.
I don't suppose that was East Palo Alto Home Depot, and either Menlo Park Hardware or Hassett Hardware in Palo Alto?

Those two Ace Hardware stores are amazing! They have so much stuff in such a small place, and always have helpful people.
A Visit to “Spiral Jetty”
BlackHat SEO. Guide to Building, Managing and Scaling Your Private Blog Network
When you say you're passing on a Samsung for that reason and you get an iPhone there is another primary reason.
The author isn't considering an alternative strategy, which is to address security issues in-place (i.e., without upgrading Django). This means keeping up on them and substantively addressing them through configuration or possibly custom code, but for something they want to freeze in time with respect to a platform, it's a reasonable choice.

Every time I've had security issues to address, there's almost always a short term fix (close a port, disable a particular eval method). In the cost/benefit analysis of maintaining a legacy app, it's a legitimate option to simply rely on those.
It is not from lack of trying. Geophysicists have been trying for 50 years. There was a glimmer of hope when I started grad school with Russians promoting pre-quake velocity anomalies and radon emissions anomalies. And Chinese promoting animal behavior. Neither were reproducible or reliable after extensive study.

Then prediction research became the black death of academic careers with little progress.

This century a milder version called 'earthquake forecasting' has gained acceptance. That is more big data and statistical odds.

Plus 'early warning' seeks to detect quakes and warn people at the speed of light, seconds before damaging waves arrive at the speed of sound.
I'm not the original commenter, but I like looking at, touching, and picking out my own food. I don't think I will ever get groceries delivered.
Then don't give them your personal information
With a kid or kids that age it might be best to take a break. When my first born was 6 months I quit my full time job to do a startup. 12 months later my second was born. A year later we sold the startup. Focus was the job and family. Learning new stuff was out of the question. I had some catching up to do when the kids got a little older but it wasn’t hard.
I think those are great examples of what I was talking about actually in the Java ecosystem.

JodaTime is now deprecated in favor of Java 8 time (JSR-310). Akka is an official library from Typesafe/Lightbend. In a JVM ecosystem, you can get this kind of stuff directly from a supported corporate vendor. You can even easily pay them for support if you want. And a lot of times stuff even gets standardized through the JSR process.

Now, if you’re in a pre-Java 8 world and you need JodaTime, sure it makes sense to bring it in, not just use only Spring. But eventually that software library gets recognized as necessary to the ecosystem and standardized, and you no longer have to rely on yet another 3rd party for it.

Whereas in another ecosystem, JodaTime might just keep existing, maybe even alongside the bad default language library, and everyone has to always be told to go get this third party dependency if you want to do things right.
Which they don't let you do, perhaps for "insurance" reasons, and if you do it, you won't have a slip with a code on it to check out with.
To buy groceries.

I dont think you intended that, but your comment seems to imply that having higher friction is an inherent experience of a grocery store, and that there is no reason to go there otherwise.
Succinctly put, thanks.
> My reading of it was that his complaint is that in keeping up with the security upgrades, Django breaks other things.

Django takes great pains to ensure that this isn't true. We don't backport anything other than bugfixes and security updates to releases. It's not like we suddenly introduce a new feature into a previous release that's backwards incompatible with your current code. If you're on the LTS release then you can be happy in upgrading Django to the latest point release with all the latest fixes.

And the Django project has finite resources. It cannot backport security fixes indefinitely which is why we have the LTS release in the first place. If you want something stable: sit on that for several years at a time, or spend your time backporting any security fixes yourselves.

Unfortunately software is a moving target, but Django tries to make it easy to upgrade from one LTS release to the next. The upgrading difficulty often comes from third party packages, which is hard to avoid in any framework or language.
Fast Cash Now: See How to Get Quick Cash in 5 Minutes with Your Mobile Phone
Those frameworks would be considered dead by most devs these days. If the last change log is dated older than a week they start to panic.
Things like this take time to organize. Surely it must have predated the libra thing?
Months of the year are named in the similar spirit in Polish, Belarusian, Ukrainian and probably other Slavic languages.

Edit: I couldn't find a good definitive source of etymology/roots etc, so here's a rough sheet of what was able to scrape from the web as well as my own knowledge/interpretation: https://docs.google.com/spreadsheets/d/e/2PACX-1vT8PGYX8c46N...
Explain how the USA has jurisdiction in Turkish territory.
Highly recommend you give CherryPy a look. Its older than most Python web frameworks mentioned (Flask and Django included) and was the most beautifully backwards compatible framework. In spirit of migrating to Python 3 they are obviously dropping old versions in a reasonable time frame though. I wouldnt recommend Python 2 for any new projects regardless.

I used it for 3 years nonstop. It is minimal so you include your own ORM of choice and template library.
Why Three Prongs? (1996)
That's still money and infrastructure in Africa's pocket in the short term, and perhaps another freight company will visit Africa if the price is right.

Of course, this all makes sense until China makes a navy for the Indian Ocean.