skysight-inc/HackerNews huggingface dataset:
This is like the whole “don’t call them drones call them UAVs.” Thing in that community a few years ago. Everyone still calls them Drones. Sorry, crypto means crypto currency now.
Isn’t this what the (mobile) web app is already? I deleted the app a couple of years ago and used the web app exclusively, it sheds much of the bloat (so far...).
Why it's an antipattern ?
> People are learning Django in 2018?

I am. So, yes.
Over the last few years Python has gained a type annotation system. The primary goals are to improve testing, improve documentation (the type information is more likely to stay synchronized than docstring annotations), and improve user-feedback in environments like an IDE or Jupyter notebook.

These are called "type hints" because they are not enforced by the Python runtime.
"Somewhere under all this shit must be a pony."
The "clusters" that support this have to be co-located in the data center - I guess they have to be on the same ToR switch or something. That gives less flexibility for deployment, meaning there's less chance of being able to spawn 50 new VM instances when you need to. Also I expect they cost more than VMs without RDMA support, whereas the DPDK support seems to be free.

I'll hopefully get chance to do some experiments soon.
Thanks for the links! Do you know how to convert a generator from Keras to an input in estimator, add class weights, custom loss functions, plug-in various Keras-based callbacks as well? I couldn't find any guide for that part.

What do you use to orchestrate distributed training in Keras?
How large are we talking? Do you consider Instagram large? If so, you should let them know they should stop using Python and Django.
Don't do what I did and use a lysol wipe from the bottom of the jar. It had too much fluid, and damaged the keyboard. Modifier keys were frozen in "on" position, and I was unable to login. Now that laptop won't even boot.
It was at such a crucial time for Slack to work and it didn't
I didn't like Blockfolio, so I built this.
I like those too and just bought a second one (2015 model) for the girlfriend. It seems a shame that they stopped making them. I guess maybe it was too much competition for the more expensive, usb2-less Macbook.
No, I respect you as an HN contributor and wouldn't offend your intelligence with that.

Since comments are public I don't necessarily address the parent poster with them, I also speak to the broader reader/commenter base.

I should have made myself clear on that, sorry.
Urban design in the United States and North America has generally been evolved in a way you'd expect. Larger spaces caused people to spread out further. North America is a (relatively) new place where people seeking land struck out from their ancestral homes for places with space.

The return to urbanization and need to be around other people is only now really starting to take hold as people see the benefits of european cities, which by North American standards are ancient.

Maybe they were that way for a reason? Imagine that...

For comparison:
https://www.worldatlas.com/articles/european-countries-by-po...

https://en.wikipedia.org/wiki/List_of_U.S._states_and_territ...
> but I believe that what we're seeing here is the biggest game of musical chairs, ever.

Nothing like it; the amount of money invested isn't huge. It's nowhere near as scary as the various national mortgage bubbles in the noughties. When it collapses, damage will be limited.
Then we are a company living very dangerously, cause any of our developers can deploy :)
- stdlib full of edge case problems causing you to second-guess and double-check things. I had to write so many libraries to wrap core classes like libxml.

- No support for multiple CPU cores

- UTF-8 is still a second-class citizen

- Not strongly typed

- High memory usage

- Slow execution

PHP and Ruby can't even serve themselves safely over HTTP and they are web languages. They offer nothing that isn't better handled by Go and Rust. Even Node is a better choice thanks to non-blocking I/O, the huge talent pool, and the ability to reuse code on the frontend, desktop, and mobile.
A 12 year old me watched this when it was broadcast. I knew after seeing the programme what I wanted do for a career. 40 years later I'm a software engineer - my teachers at school would be most suprised :)
Since everyone is going pretty much OT and assuming this will be made with razor sharp knife blades that will randomly go off into eyes and the genitals like the creator never thought of it - how weird is this one -

"Upon dropping or throwing your phone The Phone Drone will automatically pop out its propellers and rotate clockwise or counterclockwise based on the sensors readings."
https://archive.is/4qtsU

But Kickstarter shut it down, although it broke a lot of rules on top of being impossible BUT it was shut down for "is the subject of an intellectual property dispute and is currently unavailable"

https://www.kickstarter.com/projects/693592078/the-phone-dro...
Yep, absolutely. What folks are calling devops (wrongly or rightly) to me is simply what I considered a senior level sysadmin. The guys who can basically fix anything needed in a pinch - but guys you probably don't want designing and building large scale applications.

It's been a very strange 10 years to see the title of "sysadmin" start to become "IT button pusher" and the actual skilled role turn to the title of devops.
I find it utterly bizarre that they would sell off their primary domain for their software to some shithawk SEO guy. What an incredible way to ruin your credibility with customers :\

Honestly it just looks like they're hoping to rake in some cash by dumping loads of traffic onto their SEO buddy, rather than maintaining their business credibility.
High housing prices are a massive tax on both middle class and investment. It all flows to landlords and lenders. Cut housing prices by 1/2 - 2/3 and the middle class has money for other things. We need an Elon Musk for housing.
A phone that can survive a given fall 4 times out of 5 is pretty sturdy - but own and use it long enough, you'll hit the 1/5 eventually.
Human 1.0 - Humans now. A common single entity can't do that.

Human 2.0 - Sure, why not! :)
Referring to a group of 1.4 billion people, the economy, the government, the economic pressures driving each of them, et cetera as a single entity can reveal a level of ignorance about these components of a society.
Why WPEngine Is Acquiring Studiopress
One of the founders was my college roommate. Without quoting anyone, Coinbase is not selling anytime soon. At best, it might be a round of financing.
> This is not reordering though, it’s called Cesàro summation. It won’t always get you an answer, but if it does then the answer is unique and reacts nicely to sums and products.

It's also probably worth noting that, if the series is genuinely summable, then Cesàro summation gives its sum.
Looking at the table is bad enough, but I imagine most people looking would think "Aaah binary" and convert to decimal: 1, 6, 7, 4, 5, 26, 27, 24, 25, 30, 31, 28...
That's cruel :)
Inertial dampeners
Some just expanded their investment horizon and now wait 100k by the end of 2019.
What I'm saying is, the iteration step from "existing dataset" (what we have today) to "faster data traversal" (what the article proposes) is a custom file with a custom format on one side, and the appropriate query/index on the other side; one is definitely more understandable, portable and maintainable than the other.
Learn Best Practices for Node App Structure with this video lesson, just $5.99
Interesting article. I've been doing some production work with ML and I was wondering which tool would work better in my specific enviroment.

Currently I've been training a CNN model in Keras with good success, and using custom scripts to port it to a TensorFlow model. The .h5 file from Keras helps a lot with this step.

Next step is compiling a shared Tensorflow library so I can deploy the trained model in C++ (project requirement) and this has been a pain in the ass, regardless of framework...
> At most there might be one or two concepts that might in some manner if you squint hard enough could be better represented by negative base numbers,

That's what I was thinking.
Show HN: google-forms-css – Style Google Forms with Bootstrap or CSS
There's no way a single software dev in the States could live that close to work, in a nice part of a major city, and also be able to afford space to house and take care of two kids. So his story seems pretty relevant.

Besides, if you're going to do software dev you typically need to be in a city to have options, so the squeeze factor is still there. I can attest to this as well; I'd much rather take the lower rent and live further out. I never even do anything in the city.
I know this was rhetorical, but no, it doesn't
> more "eye friendly" prongs

This is a scary collection of words.
Making complicated things easy to understand is much more simple in python than in js though.
also a bit weird that having to even mention that they don't sell to shady middlemen counts as good publicity. that kind of thing should go without saying, really.
Is it not a binary search problem?
I think you're in agreement! In 2012 you could run Java in the browser. Not so much in 2018.
>>> European politicians constantly tried to emulate aspects of the American System.

Not today's system. The system they wanted to emulate was that of the 50s/60s/70s, which was a socialist utopia compared to the America of today.

No European politician today would suggest denying healthcare to sick children, or a return to debtors prisons. Those things are happening. Nevada is about to elect a literal pimp, a man who proudly operates several brothels, as a state representative. Things are very different today. Europe is not trying to emulate the US anymore.
Nothing, other than that it 1) may not work on all hardware and 2) slightly increases battery drain.

Suspend (to disk) can be slow on some hardware -- moreso than rebooting. Though it preserves state.
Amazon to Help People Start Delivery Services for Its Packages
In your very specific situation this might work. But problems that a lot of people would face:
1. unreliable local BTC exchanges that increase the risk substantially
2. local banks that will scrutinize or prohibit transfers to/from BTC exchanges
3. cheaper/faster/better options (e.g. SEPA)
4. in some countries it takes weeks to months to setup an account with a BTC exchange

On top of that, international payments are only a PITA because banks are lazy. Banks could easily make the process cheaper and faster if they were so inclined. If BTC ever gains ground in this market, it would not last for long.
" If there's a particularly nasty issue that seems to require deep database knowledge, you don't have the liberty of saying "that's not my specialty," and handing it off to a DBA team to investigate. Due to constrained resources, you're forced to take on the role of DBA and fix the issue yourself."

Wow, I'm sooo glad we've come as far as we have. I recall a time where a DBA was literally in charge of creating schemas for a product. Just about everything this person is describing in the article rubs me completely the wrong way. I am all about everyone who can help to try helping. All hands on deck. This article is pretty backwards.
Cross-platform clipboard manager with history support
It is cool and possibly quite useful. Definitely a good engineering challenge/project. Others have already pointed out some safety issues and a few others have then questioned likely are those scenarios.

For me though one of the big downsides would be while traveling. This thing would never be allowed through airport security as a carry-on. It looks like mini knife like objects encased in a soft rubber casing. Yes, one can always take it off and store it in a checked-in bag. But if you forget then you will be forced to choose between dumping it or not boarding the flight. Not to mention the extra cavity search one might get as a bonus.
Can we get a (2014) on this?
Expecto Patronuses?
DRF is nice enough 90% of the way, but when you need to do something that its authors haven't really thought of, you need to dig in very deep to fix things, I've found. :/
AI ambulances and robot doctors: China seeks to ease hospital strain
It is current year and Django is still very relevant in web development.
When I look at the receipt from my ticket I see:

FARE-USD	$ 440.	93
TAXES AND CARRIER-IMPOSED FEES	$ 61.67
TICKET TOTAL	$ 502.	60

Then when I go to the account summary and see the EQD awarded from that trip, it's 440, which is only the amount of the fare. Maybe it was only taxes on that ticket and no carrier fees though.
Depends on what you are doing.

To frame it another way, what happens if 100 requests come in at the same time for that expensive value when it isn’t in the cache yet? The expensive calculation will be run 100 times at the same time.

Ideally, you’d rather refresh the cache value in the background once and never allow duplicate requests for it from the web.

If you’re running a language that makes it easier to deduplicate requests for certain data, the original approach will last longer. The CacheEx library in Elixir, for example, will only run the expensive calculation once, set the cache and then send the value back to everything that requested it while it was loading.
Personally for me, the home computer came at just the right time. As a teenager I was a hopeless student and really had no direction other than an interest in computers. I didn't really know what that meant until I got unsupervised access to a Commodore PET in 1980 - that was the start of the software engineering adventure for me. It continues today working as a freelancer and avoiding being a "manager" :)
there's a race condition between checking if something is in the cache and actually putting it in the cache. A more correct solution would have all threads wait while one does the actual work.

This gets more complicated if you have a distributed cache and/or distributed application servers. The typical solution there is to allow at most one computation per process/device.
Especially with Sweden, I think jantelagen[0] is also an important thing to call out. Not so much in a negative tone, but more in terms of simply framing career success. There just isn't the same pressure to be a rockstar. You can be good at your job, even just ok at your job (maybe even bad at your job) for decades and that's fine.

That's not to say that ambitious and driven individuals are rare, but the amount of social judgement around career is significantly less in most circles than in the states.

[0] https://en.wikipedia.org/wiki/Law_of_Jante
> When you have a dozen developers working on the same project, doing the deployment yourself is a danger to the company.

How and why? There may come a point where it's worth segregating deployment from development, but I'm certain it's a long way north of a dozen.
Yep.

Invoking Reductio Ad Absurdum, there's always a place for us in the ghetto too, the only question is do we want to live there?
also this is not even close to being an issue with webpack
Agreed, for this reason I stopped using it, the investment in those digs were not worth the time to not copy/paste some CRUD api views. Which is what I do now, and modify as needed.

If the number of models and views grows too much and gets brittle, maybe it will be worth trying again.
It's more like Steve Jobs was such an uncompromising asshole that he would rather throw a substandard product in the garbage than put out something he considered lesser. He didn't have vision, nothing he "made" was revolutionary at all, and he didn't make anything after the NeXT. Steve Jobs was amazing at two things: getting in on the ground floor (the iphone came out so quickly after the first all touch screen smartphone that no one even remembers the original) and making sure that what they did put out either worked or didn't see the light of day. I remember the early android competitors (notably Motorola's droid) suffering from touchscreens that failed to track accurately (https://www.wired.com/2010/03/touchscreens-smartphones/) compared to the near perfect performance of the iPhone, its the sort of thing that Steve Jobs would have insisted on.
If that's your preference, great.

But again the point is that presuming goals/preferences, or attributing them to all others (and no, OP didn't do that) scales poorly.

As with most workflow preferences, the details are highly internalised.
There's a difference between the market price and valuation. “Price Is What You Pay, Value Is What You Get”

An investor might determine what they would be willing to pay for an asset (i.e. a fair valuation) and compare it to the market price. If it's selling for less than what they believe to be fair market value then it's a buy. The same methodology can be applied to sell decisions.

If I buy a house to let, I can create a model to project future cash flows derived from rent, costs, taxes etc. I can then discount the cash flows (DCF) with my target rate of return to get a valuation. Yes there are variables that are difficult to take into account i.e. likelihood of government default. It's not possible to apply a cash flow valuation to BTC.

Yes there is a market which determines the price of something. But that does not necessarily result in a reasonable price.
It is interesting to think about these trans-national corporations fighting wars and then signing peace treaties. Used to be only nation states did that.
You are drinking from the water hose. Do this long enough and your ability to concentrate will atrophy, it is a muscle that needs regular exercise. The first step is to understand what you are doing to your brain.

Try this: instead of merely skimming articles, make it mandatory to summarize everything you read in a few sentences. You'll very soon figure out that most what you read does not really interest you. Understanding requires work and deeper motivation to do so.
OSX is already proactively compressing memory in the background, if it deems a process worthy of compression.
It’s susceptible to Thundering Herd whereby more requests come in for the same cache key before the initial computation is finished, and so you end up with lots of cache misses. The fix is usually to lock the cache key and have subsequent requests wait on the original computation but it’s a bit more complex to code.
> I don't believe in choices

...ok, people still make choices though, you're not controlling their minds. Perhaps educate your workforce so they make the right decisions by themselves, it's more effective and takes less effort than trying to coerce them through generalizations.
It's not like anyone might want to take notes or something.
Oh man! I feel where you are coming from but who clicked on this link except Django fans?

That's like walking into a Django club and telling everyone their framework sucks. Even as a member that only gets you so far.

I can't believe you also called it difficult to maintain! Because when you say slow, the response its easy to maintain, and you went ahead and called it difficult to maintain?

At least give us a reason.
Did you look at Tensorflow Estimators ? They are a new high-level API with built in support for distributed training.

https://www.tensorflow.org/programmers_guide/estimators
You lose a lot of efficiency when you spread any particular software development work beyond one person's head.

But you lose a lot of expertise when you spread your developers too widely, technology-wise.
Matias? Keys just stopped working. We cleaned them (we have people who are trained techs) and they still just stopped working. Two of the keyboards just stopped working for everything. It was weird. Plus they were really cheapish build quality.

MacBook Pro - the B key is dead on each keyboard.
Both linux and Windows seems to get basic text selection right, yes.

Of modern desktop os-es, Mac OS X was the only one who has ever consistently surprised me on this.

It might not be a big deal to everyone but for me who

- deal with text day out and day

- and prefer to keep my hands at the keyboard (even when I have a nice trackpad)

small thing like this matters.

Just like details like a good trackpad matters to other people I guess.
Why the fork? ... oh LICENSE change
Erlang - https://www.erlang.org/docs

The best three entries are
* Learn - http://erlang.org/doc/reference_manual/users_guide.html
* Use - http://erlang.org/doc/search/
* Go deep - http://erlang.org/doc/efficiency_guide/users_guide.html
I'm not into cryptocurrencies at all, but it doesn't seem like a good idea to couple Google/Facebook (e.g. nonexistent) levels of customer service with a banking/investing like product.

Though, it's not like the current crytocurrency exchanges are doing well on this front (the other day there was a post about how Coinbase support is terrible), but they're small and have niche brands.

I don't see why a company like Facebook would want to expose themselves to the costs of employing hundreds of customer service reps and/or the negative PR of people loosing lots of money or access to their accounts with no recourse.
It is, but a developer that's using ORMs because they're scared of SQL tends to be the same type of developer that will decide not to look at those.

I'm not dismissing ORMs - I use Sequel (the Ruby ORM) for almost all my database access. But I've also seen enough people use ORMs as an excuse to pretend they don't need to understand SQL or understand the database to understand why some people look at ORMs with suspicion.

A lot of code that is obviously bad when the database queries are plain for everyone to see are not so obviously bad when it's less clear if that method call translates to a database query or just extracts data locally.

Note that this is a general issue with this type of abstraction: It is a common complaint against transparent RPC wrappers as well that if they're too good at hiding that an object is remote it's easy for someone to carelessly cause massive amounts of unnecessary roundtrips.
As they say in the midst of an M&A process "Always tell your old roommate what you're doing".
I agree. Here you find the whole study: https://www.rand.org/pubs/research_reports/RR2242.html