skysight-inc/HackerNews huggingface dataset:
I'd gladly pay apple 300 dollars for a copy of OSX I could run on generic PC hardware.

macOS is for me, largely just easier, for most of the things I want to do, it 'just works' - in essence, I'm paying up front, for less effort later - at least thats how I see it anyhow.

Having used the Linux subsystem in windows, I dont think I could do any serious work in it, outside of say developing a linux console application, even basic functionality like ping doesnt work (in the version I have) - its great for lightweight testing, and to have a unix shell that you can use unix tools in (sed, awk, etc) but its not the same thing as a full unix.

While I'm sure that usability of Linux as a Desktop is better than it was a decade ago, at a glance, it doesnt appear to be better enough to replicate the experience I have in macOS.

In the end, I just hope Apple releases better hardware before I need to upgrade.
Nice article, and I agree with the explanations of what makes Keras and TensorFlow best for specific use cases. Some history: I have used TensorFlow for years, switched to coding against the Keras APIs about 8 months ago. I wish I had more experience with PyTorch, but I just have the time right now to do more than just play with it.

One suggestion to the authors: the benchmark figures are interesting, but I wish you had shown CPU only results also. At work, I have all the GPU resources I need but for my home projects, which are all NLP deep learning experiments, I usually rent a many core large memory server with no GPUs (GPUs seem to speed up RNNs less than other model types).
These announcements and the resulting press coverage have been very frustrating to me because it seems only that carriers committed to selling data directly to the end users, eliminating the middle man. One could argue they can (and will) control the ultimate destination this way. Or one could argue they will just take a bigger share of the pie without someone marking up the data in between.
Test Driven Web Development with Python teaches you Django while also teaching you TDD. As long as you're comfortable with Python it should pose no problem for you. Many of the principles will be the same with Flask as they are with Django. It might even be a great learning experience if you take each chapter and build out the equivalent application in Flask as well as Django.

It's a very good book and easy to consume, and also available for free online. However, I have not read Python Testing with PyTest so I cannot compare them or answer which is better for you.
> as things become easier to do, it gives more people the opportunity to do them badly.

ala, this is why we have electron, php, and javascript. None of those things behave badly, but it's very easy to write something useable in those, but resource intensive, or insecure, or poorly maintainable.
The Ad Hominem Fallacy: How People Use Personal Attacks to Win Arguments
That just sounds like an experienced developer. X Y and Z could be Bootstrap, React and Angular. In that case you have an experienced front-end developer. In my view a full-stack developer is somebody who can write front ends, middle tier logic and design and use databases efficiently. In various phases of his career he should have worked specifically in each of these areas in depth. My view also includes the idea that a full-stack dev should understand how computers really work and should be able to spec a server/VM for a specific purpose. There are not many of these people out there. Heck, I was shocked 20 years ago at how few devs that seemed like nerds to me didn't even know how to take apart a desktop and diagnose a problem. Maybe I'm just an old guy and should worry more about the kids on my lawn.
No. You can be a senior java developer with great expertise with only a part-time job. There's nothing that prevents you from being at a senior level in multiple technologies or fields of study. More then that though, doing both complements each other, so that a senior level full-stack developer often has better insight about server-side issues then someone who only ever knows how to provide back-end solutions to product level problems.
Yes, from what I recall, any time the author talks about functional tests he is using Selenium.
How These Young Guys from IIT Delhi and Delhi University
Short-travel keyboards are, by some studies, less likely to cause RSI than typewriter-style longer-travel keyboards. At the very least, there is reason to question why emulating the key travel of a mechanical typewriter linkage makes sense versus short travel, or even no-travel haptic feedback.

I think Apple's keyboards, when they work, work really well. And you can get them without number pads so your hand isn't traversing a wasteland of wasted keys to get to the mouse.
> What's the point of high income when you have to use it to buy things you otherwise get as part of the package anyway

it doesn't just cancel out though. software devs in the states make much more money, to the point where you can easily afford the things that the government would provide you in europe. plus you obviously have to pay for those things through taxes anyway, and guess who pays the lions share of that. if you are in a high income bracket, you are always going to pay more in than you get back in direct services.
\'XBOOM\' – TOWARDS a SAFER SOCIETY
> It is really unfortunate that Europeans don’t have a sense of Manifest Destiny and Potential for the whole of Europe but instead fall back to nationalism, whenever a challenge like the financial crisis or refugee crisis emerges.

It's not that people fall back to nationalism - it's where we all started. It's just that for a perceived mutual good politicians say "let's go for it". The reality is that Europe can only really work long term with much closer political/fiscal integration. Every politician knows that, but most have made a career of not mentioning the things that people don't want to hear.

As for the European dream - that's hard. The shared cultural capital isn't there, and it cannot be imposed from above.
I found the following method to be very useful
- Use a paper map, decently large to see names of street.
- Spend some time looking at it familiarizing with overal shape of the city area of interest (probably more useful for europe where city centers tend to be quite irregular)
- Mark your key points, where you live, where you work, where friends live etc.
- Walk around your area to discover places you will need (supermarket, small groceries shop, a bar, a laundry....). Mark some or all on the map. (not so much for future reference but because it forces you to think about where they are in relation to all the rest).
- Take one afternoon or more to just walk around a wider area (maybe the city center), pay attention to what you see, mark intersting spots on your phone (if you don't want to walk around map in hand), then transfer all on your paper map.
- Take every opportunity to walk to places (again, easier in Europe).
I haven't tried it myself, but over at /r/SurfaceLinux it says Surface Book 2 "dGPU: Working (both NVidia 1050 & NVidia 1060 models) - Using the NVidia driver, bumblebee can be used to change which GPU is being used"

https://www.reddit.com/r/SurfaceLinux/comments/7kazwp/curren...

Ctrl+F("1050")

In fairness, Surface book 1 "dGPU: Not working – Not detected on any bus currently exposed to the Linux kernel, due to this, little to no research has been done"
Adam Curtis: The Cost of Treachery: CIA+MI6 Attempt to Overthrow Albanian Gov
Thats interesting to know, thanks for the tip!
For what it's worth, here's my experience:

My adviser decided (wisely) that we all needed to learn NN, and we settled on Tensorflow. That went... poorly. I've told this before: the Seq2Seq tutorial was designed for an older version of TF, and it triggered a bug that was not fixed because that way to do Seq2Seq was deprecated and a new tutorial was coming "soon". The "tutorial" was also just a code dump with barely any comments.

Eventually we had new people coming in with even less theoretic background than ours (we had read papers for at least 6 months), and that's when we realised it would not work at all. So we organised a 1-week hackathon with Pytorch, and we've been using it ever since.
>- Population growth eventually slows down when the mortality rate decreases.

But that worked in a world where people were reliant on children to work / take care of elders. I don't think the comparison between 40's occident and nows developing countries is of any worth. Also you can throw a lot of stuff in there : not the same social norms (occident is really individual centered, asia or africa don't seem to have suffered the same shift yet), not the same culture (child policies, cults, education access for women...). I really don't think your sentence is an universal rule. It happened once in a rather homogenical situations. Could we say the same about now ?

>- The population growth rate is expected to begin slowing

Expectations are not enough. And nothing will be inforced to provoke this. Also we're still above 2 children per women, which is too much considering the HUGE energy/consumption/overall spending cutouts we have to make to keep our planet and oceans alive.
Errr.... hold on ... I can build every component of a complete system, front end, back end, deployment, database.

Maybe I don’t exist.
Well, apparently :) They say: We believe that machine learning tools are so important that they deserve a first-class language and a compiler.

However, I'd like to see some numbers on how more efficient it is to build a graph in advance, given that the lion's share of the computations will be in tensor math anyway (which can be heavily optimized, and is independent of the graph).
5 years ago, maybe. You can buy flight tickets and tech hardware (Newegg) with bitcoin.
Large, stable investors don't buy gold, so why would they buy BTC? Especially now that the blockchain hype is derided rather than celebrated on Wall Street.
If you only display the images at a predefined size, a PNG (designed for that size) will be crisper than an SVG. Discovered this at a previous job where we were doing a rebrand, we were using SVGs for the logo and monograms on the website and the designers complained that they didn't look good. We compared them with equivalent PNGs and the quality was much better.

General guidance:

* Photo - Use JPG, WebP or similar

* Images used at a single predefined size, where quality matters, e.g. logos - Use PNG

* UI graphics that are displayed at integer multiples of the base size, eg 24, 48, 72 - Use SVG

* Illustration graphics - investigate trade-offs between size and quality for both SVG and PNG
5 Reasons Your App Crashes and How to Fix Them
Compile time SQL query checks... amazing! I've been trying to find a similar library for a while. Thanks for linking
I've moved to a new city fairly recently and running / cycling has worked well for me. I regularly run during my lunch break which has helped me to get familiar with the road layout in and around the centre.

It's really helped make me feel more comfortable if I have to drive into or through the centre as I now recognise a lot of the roads.
Well, a Turing complete computer is about as abstract as you can get, and so is the concept of memory, regardless of the natural laws of some outer universe, it'd probably be a good starting point to consider a turing computer except with limited memory.

The point is not to prove one way or another whether the universe is a simulation, just like there is no point trying to prove the law of conservation of energy as universal for all forms of phenomena, discovered and undiscovered.

It's just if we can show that all known phenomena can be the result of a very limited simulation, then when analyzing new phenomena, we can also expect it to be runnable on a very limited simulation,
too.

It's the same as assuming that the law of conservation of energy would apply to any new phenomena we discover. There is no proof, but it's a good starting point.
> A breathalyser or toilet can sample you twice a day. That can feed into a risk analysis that pushes you onto blood screening (again, largely automated chem detection, only nursing support required). If you're still setting off alarms at that point, you go to the specialist.

The long term, personalised health view behind this is what's interesting to me.

Medicine has a lot of wide-windows of what's normal for "people", but often the first signs of an underlying issue is that something that was normal for you at one end of a window begins to move, or change, in ways it hasn't before.

One sample of a blood test might tell you "that level is a little lower than average, but still not low enough we'd worry". But the historical knowledge that "I've actually always tended to be on the higher side of average for that measurement" changes the picture drastically.

Like you say, when it comes to looking at false positives of new tools like this, sure, a tool may be useless at giving you a one time 100% accurate reading, but if you can watch the trend of it over time that may be valuable.
While I agree, suddenly, there is a lot more 10x developers around me, and that doesn't feel right. I'll stick with my definition for my purposes, and thank you for telling me!
> Quart describes her own experience of slipping into the “falling middle-class vortex” after the birth of her daughter seven years ago, a time when she and her husband were freelance writers facing new child care costs and hospital bills.

TBH, couple of "freelance writers" deciding to have a child sounds like recipe for financial disaster right from the bat. I understand that "freelance writer" is a broad term, but most of the writers I know are very far from affording a child or two.

I understand that having a child, unlike, say, buying a sports car, is a luxury a lot of people around the world decide to indulge in even if they don't really afford it. But if you spend money and resources on something you can't really afford, at least be honest with yourself about it.
Also Dapper fan. I like mapping into objects without code generation and complicated queries are easier to write compared to LINQ if familiar with actual SQL. Only thing I really don't like is bulk inserts as it will do one statement per object. You can still use both Dapper and LINQ at same time but it might confuse others.
I think this is great advice about the psychology of learning. But also wanted to add an anecdote.

A friend is getting a degree in a field similar to biology. She and everyone else in her program have been processing their data (for at least the past 5 years) with a script written by the person in the department who is most competent with the programming tools at their disposal.

Last week, sanity-checking its output, she discovered a bug in the script that meant that every dataset processed by this program had been deeply flawed.

That means dozens, maybe hundreds of studies published based on meaningless data.

It might be worthwhile to also introduce a cautionary tale or two and encourage your students to take followup courses that go deeper into programming; learn automated testing; etc, so that they can be confident in the future that the output of their studies is correct.
I was thinking that you need to do that everytime refs change, but it's just a boost and I presume you can have some refs in the commit-graph and some not in there and it will still work, so you're probably right.
I kind of agree. I find the way the fastai library (which builds on PyTorch) is written does not match my personal preferences very well. That being said I still really enjoy working with it and the courses do guide one along quite well. I'd actually recommend it for anyone who just wants to get started and play around. It's fairly easy to get good results on a gaming box (say 1080 GTX) reasonably quickly. I also like the Jupyter Notebook approach that they use for the lectures. It encourages experimenting around and they also encourage you to dive into the library and read source code which is good. Alas I find the terse style complicates it a bit but that may very well be personal preference. It's also good to know that they try to implement interesting papers quickly.

I think overall if your goal is to use a preexisting architecture to get quick results fastai is a great point to start. If you want to build your own architecture, reach one level of abstraction lower.
Edit: I liked this PyTorch youtube series quite a bit: https://www.youtube.com/watch?list=PLlMkM4tgfjnJ3I-dbhO9JTw7...
I don’t have a case and have dropped (and thrown) mine. As long as you’re not throwing it directly into the ground the iPhone is honestly pretty sturdy.
Manifest Destiny was the spirit of the times during western expansion. The West was considered "free and empty" (Let's ignore the natives), and it was America's destiny to control the continent from coast to coast.
So not as much about expanding, and more about growing in to what room "was available", I think.
Fair enough, but it seems what PG was describing was aesthetics, not necessarily performance.
Until they experience a major medical event, survive and find shortly thereafter that they have been furloughed for "other reasons" because their insurance becomes too costly for the employer to afford.
> - the screen to 4k

If they bump it up (which would be a good idea) they'll likely go 3x (4329 x 2700 on the 15") not 4K.

> - the memory to 32GB

That's the one I don't see happening. Much of Apple's tradeoffs are about keeping battery life in the face of design stupidity, dropping LPDDR is very unlikely.

> - the SSD speed and give me options of 1TB and 2TB.

Both options exist (on the 15") and AFAIK Apple has pretty fast SSDs, the main issue with them is that they're soldered not that they're slow.
Ticketmaster will feel the force of GDPR on this one. I'll be interesting to see how it plays out.
With all this continuous effort required, wouldn't it be simply easier to ditch the whole 'use ORM because it makes life easier' nonsense and use just some SQL-mapping tool like iBatis? Where you really, truly have 100% immediate control over queries, no dancing around with logging and wasting time figuring out why the lib decided to fetch this and not that.

I honestly don't get the fear some people have from SQL. If you can't do SQL good enough for 98% of use cases out there, you are not senior dev, not even experienced one. It's just one of those basic dev requirements that won't go away in next 50 years anyway.
What if the child consents tho
"I honestly don't understand all these quality sacrifices just to make things thinner. It makes the product actually feel somewhat cheap and brittle."

Here's a hypothesis:

For many years, before the iPhone, Apple's computer business was built around keeping its loyal customer base happy. That base would buy new Macs by default, but would stop doing so if the long-term experience of using them went down too far. So Apple focused on long-term quality.

Now, their computer business is built around seducing iPhone users, most of whom who are now using Windows computers, into moving to the Mac world. The vast majority of such users base their decisions on little more than what looks best in the showroom. For that showroom seduction to occur, Macs are better off being the hottest looking computers there. Whether or not their keyboards work for much more than two weeks after purchase is far less important. (14 days being the period of the Apple return policy.)

Another factor: there is little reason for annual or bi-annual replacement of fully functioning computers any more. I'm still happy with my mid-2012 MBP. In the old days, Intel chips got faster according to Moore's law, and new software took advantage of that speed, so you really had to replace hardware at a fairly rapid pace to not experience everything getting slower and slower year-by-year. But the speed of my 2012 MPB is just fine. The situation is night-and-day different than it used to be.

So, once Apple achieves that initial showroom seduction, even if the user doesn't end up being particularly happy with their machine, they probably aren't going to buy another one for 5 or so years anyway. So customer dissatisfaction isn't going to be felt for that much time.

Moreover, from what I'm seeing, customer experience in the Windows world isn't consistently better, so word-of-mouth isn't particularly likely to pull the average user away from the Apple ecosystem and the way everything works together, and years of their emails and documents being stored in the Apple cloud which they'd lose access to, or go which they'd have to through the pain of moving elsewhere.

Overall, if making ever-more money is Apple's only real goal, focusing on thinness over all else is arguably a rational choice, as long as thinness makes Macs look sexier in the showroom.
I don't always buy bitcoin but when I buy it crashes
> They are people on the brink who did everything 'right'

One of my favorite lessons of software engineering: it doesn't matter how right you think you are.
A '30 minute commute to work' is a long time every day. It adds up to 250 hours a year, and over 10,000 hours over a lifetime.

Accepting a longer commute means more options, but the price is steap. Mine is currently 10 minutes and in a prior job I walked to work. However, that means I either need to move regularly or have a lot of options very close to me.
While I do like Apple and their integrated hardware/software platform (see my problems with Dell XPS 15 reported in another comment), this also shows the problems with a monopole producer of macOS hardware.

I still run a 2009 iMac and a 2013 MBP. The MBP is still fine but I'd prefer to replace the iMac with a desktop with external screen. But there is no hardware worth its price!

The Mac Pro is great, but too expensive for hardware from 2013. The Mac mini has the same problem, but even worse, the existing hardware isn't fast.

This shouldn't happen if multiple companies were in competition for great Mac hardware.
I guess the problem here is that the article really mixes up two different things: "continuosly existing state" and "continuosly existing civilization".

E.g., when people talk about Ancient Egypt nobody doubts its continuity even though there were at least 3 Intermediate Periods similar to periods between Chinese dynasties.
I'm sorry but you do live in a bubble. Here is a UN report on poverty and rising inequality in the USA: https://digitallibrary.un.org/record/1629536/files/A_HRC_38_....

Here are a few notes from the report:

* In September 2017, more than one in every eight Americans were living in poverty (40 million, equal to 12.7% of the population). And almost half of those (18.5 million) were living in deep poverty, with reported family income below one-half of the poverty threshold.

* In the OECD the US ranks 35th out of 37 in terms of poverty and inequality.

* The youth poverty rate in the United States is the highest across the OECD with one quarter of youth living in poverty compared to less than 14% across the OECD.

* US healthcare expenditures per capita are double the OECD average and much higher than in all other countries. But there are many fewer doctors and hospital beds per person than the OECD average.

* The Stanford Center on Inequality and Poverty ranks the most well-off countries in terms of labor markets, poverty, safety net, wealth inequality, and economic mobility. The US comes in last of the top 10 most well-off countries, and 18th amongst the top 21.

* According to the World Income Inequality Database, the US has the highest Gini rate (measuring inequality) of all Western Countries

The truth is poverty and inequality is uncomfortable and pushed to the edges of society.
Ceres Imaging gets $25M to intelligently scan crops from above
Lots of card payment details leaked in this one - a lot of the articles are trying to downplay it, but it is clear that these details were leaked and were used for fraud.

Monzo did a good writeup on it: https://monzo.com/blog/2018/06/28/ticketmaster-breach/
Still high taxes for Qantas rewards redemptions. Majorly so.