skysight-inc/HackerNews huggingface dataset:
> Last time I looked a lot of the insides were terrible.

But is it really? Speaking from personal experience it is easy to compare project with large featureset (and one with heritage) to one with scope on doing single thing and come with conclusion that smaller, focused codebase is more consistent and better implemented. At the end of day what matters is if those terriblenesses actually bite back:

- is this code changed frequently? Does it need to be changed frequently?
- is it written in a way that that makes fixes and improvement unbearably costful?
- is it written in way that allows it to be put apart? How costful are those individual parts to improve?

Django is large codebase that is worked on by different people and when time permits this, which means different parts differ in their age, practices, and ultimately, quiality. This eventually results in codebase that may give appearance of being messy.

Joel Spolsky explains this nicely in his article about old and large codebases appearing as hairy and messy to developers:

https://www.joelonsoftware.com/2000/04/06/things-you-should-...

Especially the part that follows below quote is valuable wisdom to keep in mind:

> When programmers say that their code is a holy mess (as they always do), there are three kinds of things that are wrong with it.
I build for the web so I'm obviously biased, but have you considered building a web application?

If your app doesn't use device features that are not exposed to the browser, building a progressive web app (https://developers.google.com/web/progressive-web-apps/) will save you a lot of effort, help you get to market faster, and spend far less money on user acquisition than a native app. On iOS, PWAs look and feel no different from regular websites. On Android, you get access to native-like features, including support for loading the app offline, push notifications, the ability to install the app to the homescreen, a separate entry in the task switcher, etc.

I wouldn't build something like Snapchat or Instagram as a webapp, simply because building those experiences in the browser and getting them just right is still kinda hard. However, most applications aren't Snapchat or Instagram, and a prototype certainly doesn't need that level of spit and polish.

You might still choose to build a native app somewhere down the line, but starting with a webapp gives you a chance to evaluate your idea and get something working in the hands of your users very quickly.
Check Best Time to Fly and Buy, Using Our Flight Price Predictor
Netflix is great when you have kids. Uninterrupted cartoons with no commercials where you can pick suitable shows for any age group, properly translated, always available. Their original series there don't seem to score too highly yet (kids hate all of them aside from Lego Friends), but there's enough on offer.

I did drop down to the cheapest, lowest end subscription though. I stream via a Wii (kids don't mind the quality) and because of the DRM restrictions in browsers, I also only get to see the low quality streams anyway.

I'm hoping the stronger position of their Netflix Originals can eventually tone down the DRM crazy-ness.
>I'd love to have more insight into how this happened

There's the one story that you can read in articles like this, which will provide details of the rise and fall:

http://www.vanityfair.com/news/2016/09/elizabeth-holmes-ther...

But, there's another side: it happened because you weren't allowed to question Elizabeth Holmes. The beauty of the Internet is its natural history keeping. If you want more insight into how this sort of thing happens, look no further than early discussions about Theranos on these very boards. It was difficult to be critical, and supporters implied that the naysayers were merely "sexist". Of course, this was happening when tech industry sexism was peaking in the news cycle, and I belive that quieted some criticism.
Converting images to ASCII art (part 1)
Multi-layer RNN for character-level language models in Torch [GitHub]
the article is about netflix removing bought content and replacing it with their own stuff

edit: old -> bought
Going back to the white blood cell count. The gold standard is flow cytometry. If there is an interferent in the sample, or if the cytometer raises any flag, in some labs the backup plan is to do a manual count (100 cells) using whitefield microscopy ... are you really concerned about sampling problems?
I disagree that the post is 'substantive'. Opinions are shared, possibly reasonable one, but there is no further substance to them. I also consider words like 'steal' to be loaded in that context.

The problem is, this raises the question of sock-puppets being used; even if they don't appear to be employed as expected.
And to quote Tracy Alloway, also Bloomberg: "you can replace the term 'distributed ledgers' with 'shared Excel sheets' in about 90 percent of talk about blockchain and finance"[0]

[0] http://www.tracy-alloway.com/?p=577
The opposite of "original content" isn't "old content". It's non-Netflix content.
I have a Python 2.7 project that has been running smoothly for many years now and I'm having trouble finding a reason to upgrade to Python 3. The project uses the unicode type to represent all strings, and encodes/decodes as necessary (usually to UTF-8) when doing I/O. I haven't really had any of the Unicode handling problems that people seem to complain about in Python 2.

Can someone explain what benefit I would actually gain from upgrading to Python 3 if I'm already "handling Unicode properly" in Python 2? So far it still seems rather minimal at the moment, and the risk of breaking something during the upgrade process (either in my own code or in one of my dependencies) doesn't seem like it's worth the effort.
FbStart – Facebook for Developers
I see one like this in nearly every Tully's and Starbucks in Kyoto. They don't have as many bottom-washing options, though.

Still waiting for someone to explain the difference between "bidet" and "behind"...neither one seems to function in the advertised manner.
Swoole 2.0 will support native php coroutine
Two way street here so since you used the general term "Asia", I feel obligated to point out that in large part of Asia, the symbol is known and when liked it's exactly for what it's seen as in the west.
Is that fixed now?
I remember getting this the wrong way round myself too. It's not obvious either way which way it 'should' be, so it is a terrible naming decision.
Alternatively, when a protocol "moz://" does pop up, they can just register the domain 'a'.
They have already won. Facebook is the new TV. It will take major scandal to bring new national regulations into this media.
>Solution?
You said it yourself: "[...] our body's joints [...] were not designed to remain in one position for too long."
Try a pomodoro-esque schedule (25 min work, 5 min rest) where you get up and move around, maybe do some stretches and warm up exercises?
Time to introduce Python 4.
If everything fine with Python 2 on the current project, why bother to upgrade Django 2.0 which will break the compatibility?
This is so romantic ;)
It's not just Jains (it's almost all Hindus as well), and the original Swastika [1] really doesn't have anything other than a positive connotation. It's considered to be an auspicious symbol, something which brings luck, prosperity etc. Even now if we buy something big (like house/vehicle etc.), the first thing religious Hindus do is get the ceremony done for making it 'auspicious' (by a Hindu priest), and drawing Swastika on that property is an important part of it. The people in US, if you visit any famous Hindu temple there, you might observe a priest doing the same ceremony with someone's new flashy car.

The symbol is also used in almost any important life event in Hindu culture.

[1] https://en.wikipedia.org/wiki/Swastika
We just cancelled our Sky subscription because we'd eventually realised that none of us was watching "live" TV.

I binge watched "The Crown" during a recent bout of flu and was deeply impressed.
Nice example. I was learning Rust over Christmas so I see how it works. But one issue I have is that from the outside it's not obvious that your `close()` method will take ownership of `self`. I'd probably prefer it if there was some (compiler-enforced) convention that made it obvious to clients that `close()` would consume `self`.

As it stands, Rust code can break the principle of least surprise, since what happens in a method can affect the associated instance variable (in this case `open_socket`). A user could easily write several lines of code and only discover that `open_socket` has been moved into a method at compile-time.

I found myself having very small coding-compile iterations when writing in Rust to catch issues like this (but that was also undoubtedly due to the fact I was learning).

Is there a pro tip to avoid this issue?
Hey, we gotta eat. If people won't pay for software licenses then we'll make them pay for training and consulting services.
Can you help educate me, then? The people vote for representatives. And then....? Exactly what part of the process are people not doing, or not understanding? Is there some extra step involved?

People tell their elected representatives what they want all the time. And people get ignored all the time. This is because the democratic process in our country is not simply citizens and politicians, it is also special interest groups, corporations, and a super-rich class whose interests supercedes the people's. And within the process, there are people who are paid to influence politicians for all sorts of groups, from citizens to corporations to foreign countries. Politicians have to weigh all of this, which is very difficult.

But as far as the citizens, who are the subject of the justice's comments, are concerned, they only need to vote. Requiring all the citizens to be involved in political action committes just to, for example, retain their basic civil liberties or stay out of foreign wars for oil, is ridiculous. So, what is it i'm missing?
A lot of the same points apply with Telegram bots, though I suspect the Telegram user ecosystem is a lot less ... refined ... than the average FB Messenger ecosystem.
It's a welcome addition. I work remotely and virtually all our correspondence goes through slack, it's quite easy to lose important information and the search isn't that great.

However the problem is if you use Slack for anything other than transient information then you increase the problem with information sitting in silos, already we've got transient information in slack, information in the project management software, information in the kanban type software, information in issues on github, etc. You add Slack into the mix and it really gets hard to remember what is where.

A service to pull together all the information is probably the next killer product.
"Fairness" is an imaginary concept.

Inequality on the other hand is quite a natural concept, as in you see it everywhere in nature and the universe.

There is no known process happening in nature that is trying to achieve "fairness".

Temporary stability and equilibrium on the other hand is achievable. And technological progress is naturally inequality increasing/destabilizing to such systems.

Tigers in nature don't just grow sharper claws or canines to be "disruptive". It happens only in response to an increase in the number of prey. Which usually happens in response to more grass on the plains. Which is in response to more rains and so on.

If the tiger starts evolving hunting efficiency at a faster rate than the deer evolves defensive features like speed, hearing etc the tiger will kill more and the entire system will soon breakdown. see https://www.youtube.com/watch?v=cVOHgztZ3XI

So to say "fairness and technological progress aren't mutually incompatible" is just not true.
I was talking about today's reservations as a legal vehicle to allow perpetual group ownership & administration of land, so as to preserve it for a culture. I may have forgotten the part where, once the structure is set up, owners would voluntarily add their property if their shared this objective.
I am fairly young, 22, mostly sitting in front of the computer, even sitting while studying. So it could be said I sit around 10 hours per day.

When I was younger, up until the end of high school, I used to do sports, but since I got to college, I simply stopped caring. My body is skinny, really skinny, I weight 61kg, and I had that weight for last 7 years. But one day I thought maybe I should do something, not for the looks, but for the feel of my body, and physical body exhaustion just feels healthy sometimes.

So I thought running might be what I am looking for. Any advice on that? I am sure someone is doing it so (with lower body weight), any advice or thought on that? Btw when it's not winter, I skate, especially in summer, I use to skate all night, for 5-6 hours.
> "Greece ... was in the same situation as 10 other EU countries"
not really - Greece is especially troublesome, because it was not able to collect enough taxes from its own citizens and businesses, and also there was huge corruption.

> "Of the government support "given to Greece" between 80% and 90% ended up propping of foreign banks."
Yes - the alternative was to cut Greece out of the loop and only save the banks. Also, you have to consider the public sentiment of helping countries: in a lot of them, people made (and sometimes still make) much less money than the average Greek. So why should we send them money, people ask?

Now don't get me wrong, I think the EU help for Greece is a good thing, but also let's not kid ourselves - the country borrowed a lot of money and spent most of it very ineffectively.

>"Greece is a sovereign state and should just have the choice not to repay it's debts."
And it does. What it does not have is the choice to stay within the Eurozone and not repay its debts - such is the thing with international bodies, they have rules and you must adhere to them to stay in the club.

>"And frankly, the EU knows perfectly well what it's doing to these people"
Thing is, the peripheral countries were given a _lot_ of money during the last 30-40 years in cohesive funding etc; the wages and living standards climbed accordingly; people got used to it. Then the financial crisis came and coutries which invested wisely were able to withstand it, others less so. Without the EU, the Greeks would be poor (look at the Bulgarian or Macedonian GDP per capita); the EU gave them a chance to change that; it does not seem they used it well.

> "Any system in which a majority of the population does not have the option to block laws is not a democracy."
Never heard such a definition. Anyway you are saying that a majority of EU population does not have the option to block laws? I don't think that's true.

>"Start reading there, read at least the next 2 pages, then continue here"
Or maybe you could tell me what your point is.

>"The council stop is a joke"
No it's not, the Council is in fact the most powerful body of the EU, and decisions there are taken by heads of the countries. I don't like that, but it's the current state of affairs.

>"the legislative power is 100% in the hands of the EU commission"
Which, again, consists of people nominated by the member countries.

>claiming that this huge mass of people experiences this "era" as the "most prosperous ever"
Good thing then I don't claim that. ('most', as I said)

>"It is neither the fault of these states"
Oh but it absolutely is. Companies don't employ new (young) people, because it's way too expensive to do that if the national legislation makes it so. On the other hand, there is record low unemployment in some countries (at least czech republic, slovakia, possibly poland, and I think also Germany, possibly others). So evidently some countries are doing something good.
See also my point about some countries not investing effectively.
Right, that's more or less my question. (I'm not actually using Django though.)
The Django project has added Python 3 compatibility in Django 1.5 as experimental. It remained experimental in 1.6. It became supported in 1.7. They announced around that time that Django 2.0 would only support Python 3.

Then, they released a first 3.x compatible LTS with Django 1.8. Then they released 1.9, compatible with 3.4 and 3.5.

They then release 1.10. And they are releasing 1.11 soon as an LTS, which they previously announced would be the last in the 1.x branch and the last to support Python 2. It will be supported for AT LEAST THREE YEARS after its released.

Good lord. If the deprecation and evolution gets any more progressive, it'll compete with darwinism. And yet,
alanfranzoni complains about it. And YOU COMPLAIN ABOUT IT elsewhere in the thread, saying they're "screwing their userbase" and "leaving their users in the dust".

Don't you think you're being a little fricking entitled? This is an open source project and they're doing quite literally everything right.
Behind is for anyone's rear end. Bidet is for women. Not sure I want to explain more fully ;-)

It.... takes some experience... But definitely worth it in my experience :-)
Couch to 5K should help.

http://www.nhs.uk/LiveWell/c25k/Pages/couch-to-5k.aspx
Until they vote to change the laws and cancel all that debt.
I think he has confused the US economy with its controlling parties.
so, only if you have an account, I guess
It has always seemed to me that Python 3 was mainly a fix on the philosophy of handling strings, but that it didn't offered a clear practical advantage for programmers already handling strings with care. I don't think there is a practical reason to upgrade to Python 3 in terms of language design. The reason will be in term of survival as the community seems to be willing to follow the Python 3 movement and official support for Python 2 ends in 2020.
Just wanted to add a slightly off-topic note:

> At the time, an exploit for a software weakness in Skype was being traded online, and this exploit could be used to remotely and instantaneously disable any Skype account.

According to this article [1] blocking someone's account is still possible.

[1] https://hub.zhovner.com/geek/how-skype-fixes-security-vulner...
easter egg that won't work in any other browser, hence making it harder for people to find mozilla and switch.

I just can't even
No matter what you do you won't please everyone, people really hate change.
Can you really trust onunload handlers to finish?
I don't see any "strength" in the classical object oriented programming model as found in C++ or Java. Actually, in modern programming composition is considered superior to inheritance.

The interface concept of Go makes programming with composition much more flexible and powerful than with the class model. The author skips this Go specific and original interface typing. This provides a multiple inheritance equivalent without all the complications on C++ and that most OO oriented languages forbid because of that complication.

Go is a very original language in this aspect as well as with concurrency. Understanding and mastering these properties goes beyond simple syntax analysis.

To me the most remarkable property of Go is its simplicity. As I explained to a friend who is a strong advocate of D, the difference with other programming language is the same as dealing with a spoken language of 1000 words instead of 10,000 words. It's true that the language with 10,000 words is more expressive and richer. But the effort required to learn, read and write a language of 1000 words is much lower than a with a language of 10000 words. I'm beyond 50 years old, and too me this makes a huge difference. The best way to express it is that with Go programming is fun again. I hope that Go will preserve this simplicity. At the beginning Java was simple too. They later killed it to the point I don't want to deal with Java code anymore.
Oh, how badly I wished Americans had a clean way of cleaning their ... bottoms during my 8 years of stay there. Thankfully, Amazon had nice portable bidets which you could fit in your home toilets, but everywhere else it was still the same.
Says who?? Someone with delusions of grandeur, obviously. Because that's not up to anyone to say. Python 2 is obviously NOT going away any time soon. You can't just look at reality and claim the opposite just because it pleases you. Python 2 is here to stay and is in MUCH better shape than Python 3, in terms of actual production usage globally. Python 3 is a bad joke that someone wants to force down people's throats for NO good reason at all.
Yes and the remaining are mostly "company x made a new product y" without really giving any evidence that will have any success in the market or any impact on anything whatsoever.

More a collection of press releases than a serious attempt at prediction.
Celery is an interesting one. The code looks well written, but I found contributing to be a real pain and documentation a mess, especially compared to Django's docs.

Also, up until recently it was a one man job by Ask Solem. He's done incredible work making this project live and I am grateful for that. However I fear others have found it hard to maintain as well, slowing down progress on a very popular backend python project.
Python 3 is already a fork.

The problem is that Python 2 cannot evolve freely alongside Python 3, because even if someone wants to maintain it and keep releasing versions, the Python Software Foundation won't let them use the name Python (there was a post some weeks ago about someone who actually tried). So there is no free competition between 2 and 3. 2 has been basically killed by a decision from above.

Don't get me wrong, I'm no Python 3 hater. In fact, I have some projects in Python 3 and I would leave Python 2 if I could. But I, like many people, have to code stuff that has dependencies on Python 2, and the way they have handled the update bothers us for no good reason. In fact, the whole schism fiasco is making me use less Python and more Java, where my stone-age code still runs, lately.
While the admin code is kinda messy it's still easy to extend and customize. I'd be somewhat surprised if you could make something that dynamic and not be at least a bit messy.

I myself and also other people I know have written quite some domain-specific applications almost entirely within the Django admin, which are as a result: secure, fast and easy to use, which in some cases are not just a bit better than the existing commercial tooling in these domains.
A hint for #1: don't assume a "like" is a like.

The default emoji in a conversation can be changed by either side, on demand. So don't be surprised if suddenly you start getting a scared cat, or a tomato, instead of a 369239263222822. Why would people change the default emoji when talking to a bot? Why not?

Hint #2: default emojis can be sent in several sizes, depending on how long the user holds the "send emoji" button. From what I can tell, 369239263222822 is a small like. There are at least two other sizes. This is not some obscure feature, people use it all the time, so be prepared.

--

In general, it's worth to pay attention to details of the platform one's developing for ;).
Last update from 11 months ago, doesn't bode well
I used to know my ICQ number by heart, 300043 something.
This is straight spam. OP posts nothing but this site. It's all content-free listicles. This one is especially uninsightful. And the very first entry is very obviously paid placement.
The discussion about ARC vs GC would be very interesting. Is there a transcript anywhere for the hearing impaired?
Performance, glamour and functionality together. Great article!
This is the beginning of the Python 3 nonsense, not the end yet. It will end when the Python 3 joke is scrapped and replaced with Python 4 as a SEAMLESS continuation of Python 2.
Investing Is More Luck Than Talent