skysight-inc/HackerNews huggingface dataset:
well, that could be easily solved by prohibiting eval?
yes, forgive us for trying to resolve an essential issue of how our tech isn't green nor is there lifecyle management even on the horizon...

i see that apple and their ilk are expressing pure altruism.

because that's what consumers need, more convenience...
well, Apple has created a good deal of inconvenience, what with iTunes confusing "management" of all iOS devices and all... but god forbid anyone be inconvenienced on the way to the cash register...
this seems interesting, perhaps you could explain your more sophisticated concept.
Yes it can https://github.com/rollup/rollup. Webpack 2.x can also do this.
I’ve Just Liberated My Modules – Azer Koçulu's Statement
Blow minded!
Does WhatsApp UX Influence Romance?
So have libmath depend on libsin, libcos, libtan and libsinh. People who want the kitchen-sink version can get it. People who want just one specific submodule can depend on that. What's not to like?
This reliability is not that hard: take a photon and split it though a beamsplitter. One path leads to a detector with "you won" and the other - a detector igniting an explosive.

So why there may be problems (like: photon was not detected due to finite sensitivity) in this setting the wounded-but-not-dead outcome is negligible. In general, it is easy to amplify quantum effect with such avalanche reactions.

When it comes to MWI - it is the hard part. I am not sure if I believe it; or what is it's interpretations (maybe it's still unethical to having mourning families and friends in 1-\epsilon worlds). Also: even if I gamble many times, and I find myself alive - does it mean is it correct? And even if - there is no way of announcing it.

And also, on a funnier note - Everettian dating: https://www.youtube.com/watch?v=vBkBS4O3yvY
> allows me to interact with my phone without necessarily having to take it out

No offence, I'm sure you love this device, but to me this sounds like a wafer-thin marginal improvement that does not seem worth the effort required to keep yet ANOTHER device charged. Seriously, we're talking 2 seconds saved per look? If the argument is "it adds up", you're looking at you smart device (phone or watch) too much! With the watch you then you have to decide whether or not to take your phone and fiddle with it. IMHO everything on this list works as I want with a phone, except checking the time, so I have a Swatch from 2004 for that (which has a replaceable batteries that lasts years each).

Smart watches as they currently exist fulfill a manufactured desire (again, IMHO!)
> Maybe some people have so little to do that they can author or find a relevant package for every single ~10 line function they need to use in their code and then spend countless commits bumping project-versions and updating package.json files. I have no idea how they get work done though...

Rather than copy paste someone else's unmaintained thing and handle all the bugs, or write their own code and unit tests, they use the same library as a few thousand other people?
I would say it falls into the "Don't abuse it" category
I would pay $10/month to lease a handheld 'gun' that would terraform mars. But it must be handheld. I'm not lugging around a dang suitcase with me on my mission to populate mars.

Or, you could build a Transmogrifier. But that's not my idea, that's the idea of Mr Bill Watterson.
Responding to Uncle Bob’s comments on test-driven design
I just bought a PTS, to replace an LG G Android Wear watch which I can no longer stand.

It's slightly terrifying how much better the PTS is that the G, in every possible aspect, despite technically being worse. It's got less RAM, it's got a slower processor, it's got a smaller screen, it doesn't have a touchscreen... but somehow it ends up being a vastly nicer and more useful thing than the G.

I think that partly it's to do with different expectations. The PTS feels like a watch with lots of cool features. The Wear feels like a lobotomised smartphone which would frustrate me every time I use it.

But there's a lot of really careful design in the Pebble which is missing from the G. The UI is amazingly fast --- you never have to wait for it, ever (unlike the G). It's well designed and I can find things, unlike the G with it's weird U-shaped settings menu. I control it by pressing buttons, which is fast and reliable and, critically, means that the screen's not covered by my fingers; the G was controlled by sloppy touchscreen swipes that it wasn't very good at recognising.

Also, the PTS has a 10-day battery life and a screen that I can see in direct sunlight.

(The PTS screen is a thing of beauty. It's a reflective Sharp Memory LCD, and you can see it in direct sunlight. Like, it looks really good in direct sunlight. The colours have this metallic tint to them which the UI design shows off nicely. It's small, but so, so much nicer than the G's screen.)
But hardly anybody in software does deliberate practice, everybody learns on the job by just trying to solve the problems they are faced with at the time.

Nobody considers what their weaknesses in programming are, invents a program of exercises to remedy that specific weakness and then does those exercises every day for a year. That's what deliberate practice is.

The book was about 10,000 hours of deliberate practice. As long as nobody in software does that, it's simply not applicable to software.
In Cambridge, it's sadly a pretty artificial bubble. With all land there is in the surroundings, it looks like an artificial limit in the demand.
> Can some smart watch owner please explain what they like about having the watch?

* When a call comes in, I can see at a glance who's calling and dismiss the call without taking my phone out of my pocket and carefully do the right swipe gesture to dismiss the call without accidentally picking it up.
What a good book that is! I am reading Kageyama for the third time now, always coming away just a bit stronger.
Leftpad-rs
You could, but that's going to be the unloaded cost of a developer, add another 80k for benefits, tax, and everything else that comes with an employee. Even after that you've got a single kernel developer who might have learnt enough about the particular part of the kernel you're having problems with. Assuming its the kernel.

Either that, or pay 80k to Red Hat, who have dozens of kernel developers one of whom probably knows about your issue, and if it turns out not to be the kernel probably have someone on staff that can investigate that as well. Worst case they know who to contact upstream to dig deeper into your issue.
They do have Azer's consent to publish the mails he wrote, right?
The author missed the point about modularity in Javascript.

Small packages done right, well tested = maintenable, reusable, stable code.

The problem does NOT comes from packages. The problem comes from un-publishing public packages and centralized repository server.

I have a java project with a lot of dependencies. Does it mean it's bad ? No, but if maven repos are closing tomorrow, my project will not build as well.
Put sensors in your garden with Botani.st
Still work to be done, but def could be useful
Daily newsletter for you to discover content, books and stories related to tech
TIL 1 is a capital letter.
I love my Apple Watch, but have to admit I mainly use it... as a (beautiful, IMHO) watch.
As I recall, we discovered back in the day that my dads ford key would lock almost any ford he came across, but not unlock them.
Because the vast majority of these people don't have the slightest clue as to how computers work. No troll, no bully, no malice. They don't know and they don't want to know. They deliberately wish to remain ignorant, as evidenced by the offence they take and rationalization they make whenever someone tries to explain any of the realities of modern hardware to them.

WEB SCALE!

IO BOUND!

Forget assembly, they refuse to learn even the most basic and incredibly important consequences of the memory hierarchy. It's garbage collection and best practices all the way down.

I don't want to make fun of people. In fact, I can't make fun of people because the overwhelming majority doesn't appreciate the joke.

All I want is for people to give a shit.
It's a bit unfair to link to a version of their page which is two years old --- the current one is completely different.

As for the bezel... it's not actually a big deal in real life. It looks way worse in photos. I was concerned until I had a chance to hold one in my hands. I think it's because that watch interactions tend to involve very focused attention for very close up. If you get a chance to try one in real life, I'd recommend it (actually put it on).

I imagine the reason for it is simply that Sharp Memory LCDs don't come in very many sizes and they need somewhere to put the works; i.e., a technical compromise.

(I would much rather have the small Sharp screen that a bigger OLED. You have no idea how much nicer the Sharp screen is.)
Many causes behind this - saying the Chinese are to blame is glossing over the issue IMO and is very much akin to saying tech workers are behind the property issues in SFO. There are more sides to this...

One of major contributors to rising property prices is the gutting of trust in the stock market or any speculative market for that matter, over the past two decades. Super low interest rates haven't helped either with people looking to park their cash left with property as the only safe place which provides a rate of return.

With regards to Chinese buyers, there is some truth (again stressing that it's only a part of the picture). For the past 20 years nearly every trading partner with China has incurred a massive balance of payments deficit. That money's coming home to roost (literally). The same thing happened in the 80s when Japan was an exporting powerhouse - they bought real estate and companies across the US and Europe, pushing up the price of real estate.

There was actually an excellent piece in the Prospect by Andy Grove (former Intel CEO) which lamented the loss of manufacturing in the US and the effects it would cause:
http://prospect.org/article/andy-grove-trade-globalization-a...

Again just a facet to the picture, but you put all these pieces together and you can see the problem a lot more clearly.
There's still another eight days until April first.
The problem is that those Chinese are pushing home prices to the sky, if they continue like this Vancouver will be no more than an empty city used for trading and no more...this is pathetic
If those functions are reusable or complex enough (partly due to deficiencies in javascript the language, sure) then why not?
There will be a fork that allows concatenation of multiple tweets.
OT but apt to this community - That's what I thought, but after a lifetime of 'correcting' people, I looked up the definition of sarcasm. Turns out that the sarcastic-sounding truths I'd been deploying for decades were indeed by-the-book sarcasm rather than 'I can't believe it's not sarcasm'.

Key quote from brilliant word-talking-guy Henry Fowler: "Sarcasm does not necessarily involve irony [but it often does] ... The essence of sarcasm is the intention of giving pain by (ironical or other) bitter words."

So, we circle back to Node.js by way of pain and bitterness. Sounds about right.
@TickleSteve below me: "without this, removal is only performed within the compilation-unit"

Not quite. When you link to a static library (.a) with lots of .o object files in it, only those object files will be linked that are actually used by your program.

I first learned about this when I looked at the source of dietlibc, and wondered about every function being in a separate file. That enables the aforementioned trivial optimization, even without -flto.
Ask HN: Does Karma affect the rank of a submission?
I understand that going to the 1st page of HN needs people to upvote but does Karma affect the ranking.
e.g. A & B shared 2 links at the same time.

A's account (10 Karma) shared a link, got 100 upvotes within an hour.

B's account (2000 Karma) shared a link, got 100 upvotes within an hour.

Will B's link get a higher rank on the top page?
Or maybe some people just want to make a cool project for themselves and learn stuff along the way.
From their website: de, en, es, et, fr, it, nl, pl, pt, ru, sv.
>How would you prevent this type of attack while retaining the keyless start and entry feature

I get that regular keys could be copied and locks picked, but I feel that if you can't securely do wireless unlock and keyless start, then don't put it in.

The car industry has a lot to learn about security. I almost refuse to believe the stories where hackers take over the onboard computers via the entertainment systems in a car, because I can't believe that anyone would be stupid enough to link the two system. Yet, companies like Jeep seems to believe there's a reason that the computer running the GPS and radio needs access to the breaks.
When they say "Chinese" these discussions about real estate usually mean Chinese citizens, not ethnically Chinese locals. It doesn't seem to be explicitly said here but I'm pretty sure that's what he means, see the other paragraphs talking about government investigation into offshore buyers.
Because the standard library is where modules go to die. Slaving the release cycle of a library to the release cycle of the language is bad for the health of that library, especially in the case of javascript where code often has to be written to run on old browsers with old versions of the standard library.

Now having a metalibrary that depends on a curated collection of popular/useful utilities is probably a good idea - but isn't that exactly what many of the libraries that broke due to depending on left-pad were?
No idea, but is it possible there were actually 160 employees and the count after layoff was 120 employees? That would be 25%.
He seems to have 1 post per week in recent months though. Slacker.
The one I knew was 'practice makes permanent'.
Odd, the ones I use all have tests, thousands of downloads, and active bug trackers. If I reinvented the wheel, or copy pasted, I wouldn't get those things.
This isn't forgetting to program, it's a deliberate choice as to how library code needs to be organised. We can disagree about choices made, but let's not assume other people aren't able to code as well as we think we can code.

That being said, I think this is a perfect example of where a good concept (small, tightly scoped modules) is applied dogmatically at the cost of the codebase. It's the node.js equivalent of AbstractRequestFactoryFactoryFactory stuff you see in Java, and the Mock Messes you see in Ruby.
There is also a big programmer efficiency to be gained by having batteries included library: The new person coming to a project has learned the same batteries already, and it need not to re-learn new set of minipackages the last person working on a project has used.

In fact this should be the key selling point for stdlib to JavaScript. It actually saves money from their employers if trivial functions are mostly in the same place.

However pushing a stdlib is difficult there is a lot of hate for Python's "kitchen sink" library in JavaScript world which is totally misplaced. It maybe founded on fact that you should then minify the whole package to use one function in it, but this could be solved with dead code elimination (with proper type checking) in the minifier.
1024 x 1024 * 4 bytes per pixel = 4MB. Ok. There's no software engineering problem there, just bafflement at wanting almost as many pixels as would vertically fill a 1080p screen, for a fucking icon.
> Any search will have to rely on developer-made documentation, and/or meta data. This is great in theory, but documentation is rarely well maintained, and/or someone changes the code but neglects to update the documentation.

This is why types are better than textual documentation - the system enforces that they're kept up to date.
It’s No Mystery Why ISIS Picked Brussels as a Base
Can you tell an example problem that you solved by decompiling visual studio dll(s)?
Nexus 5 is 2½ years old and is still supported.
> This point is addressed in the article, the point is not to have web app perform as fast or better than native app. As long as they are fast enough it's ok.

That may be true if you only care about performance, but what about battery usage? That's something important on a phone.
Show HN: Haskell Package Integer.IsPositive
Yep. Everyone mocking NPM and the javascript community for this ought to retire, they clearly don't understand how to program in this day and age. Or is that not what you meant?
That's just too vague to be useful.
The same could be said about non-QWERTY keyboard layouts but I think the potential gains from using the best tools you can are so big that you'd have to be using shells where you're unable to customize a substantial amount to end up at a productivity deficit.

I find that I mostly use systems that I can make match my setup...
> OO got no rights whatsoever to highjack the benefits of the modules.

You're the only one who's trying to make that assertion. It's a strawman, and a poor one at that.
I never read in my original language anymore. Seems like the whole universe writes in English now.
Sexism is still a thing at Microsoft’s GDC party
AI is becoming a marketing word just as big data...
Risky Rats Give Clues on Brain Circuitry Behind Taking a Chance
I'm pretty sure it does not.
>Fish and oh-my-zsh both take about 5 seconds to init though

Greatly disagree on the fish startup time, for me it takes approximately the same time as bash. Can't comment on zsh though.
Not that I agree with micro modules (I would rather see a set of js core libs), but your code fails with empty strings.
It's not unheard of for ships to be overwhelmed by heavy seas. Here's an accident investigation report into the loss of a large freezer trawler in storm in the Barents Sea. The ship was thought to have lost steering, went beam on to the seas and was overwhelmed due to an incorrectly secured hatch. https://www.gov.uk/maib-reports/sinking-of-stern-trawler-gau...
Ask HN: What are some untold facts about startups?
What are the dark sides?What are the harsh truths?Are start ups reliable as a career path?What is the reality behind all the hype around start ups?
Renting isn't a short because you don't profit when the market goes down. And you are still out rent.
Apple zero-day vulnerability fully compromises your devices
How to sound smart on Medium
Show HN: Rewrite package.json to get dependencies from GitHub instead of npm
After reading this, i don’t think i’m capable of ever complain about OOP again. Whenever you think you’ve seen it all, web developers always manage to come up with something worse. The only thing more depressing than this is the comment section below the article.
D.C. regulators approve Pepco merger, creating largest utility in the nation
We had, and still prefer (looking at npm stats) the async module. Eg:

promise.then(function(){}).then(function(){})

is not substantially different than:

async.waterfall([function(){}, function(){}])

Promise advocates kept pretending async didn't exist though, and everybody was using callback hell.
Heart rate at gunpoint
Scottish/gaelic "fein" is pronounced "hain", meaning self/yourself.
That code fails in a whole host of cases, kind of proving that sometimes trivial "just one line" functions aren't actual that trivial to get right.

edit: fortunately there's an npm modules you can included to fix it...
I'm replying to two people upset about the ridiculous resource usage of simple modern programs. Bring it up-thread if you want to defend against literal waste, I'm just talking about why it happens.
$2B+ in Letters of Intent Pledged for Aerion Supersonic Jet (2008)
You mean, help to gentrify some other place?
It's for making them look smooth on high-dpi displays. Those pixels aren't drawn 1:1, obviously.
This is very similar to the famous "How to sound smart in your TEDx talk"

https://www.youtube.com/watch?v=8S0FDjFBj8o
I never knew this was considered weird until right now. Music + Shower = Glorious Morning.
I've got an Android Wear device that sits in a drawer because it is pretty useless. Charging it every night is more hassle than it's worth. I don't like wearing watches though. However now I wear a fitness tracker (Garmin Forerunner 235) because it is useful to me.
It lasts 5 days on battery, it has GPS built in so I don't take my phone when I run anymore, it tracks my sleep and has all day HR monitoring and best of all it connects to my cycling sensors so it replaces my cycling computer.

It also has basic notification support but that is the least useful part. Getting notifications on a watch saves me about 2 seconds and is not worth wearing a watch and charging it every night.
"toy for bored suburban residents" + "Plus I always wanted to fly on the Concorde" = flying on the Concorde as a toy for bored suburban residents?
Certainly they are different teams.

My comment just meant that I needed 1 hour to find a way to get a shell in a couple of their servers. That is more worrisome to me than the NSA snooping around. And I'm not a great pentester, I probably wouldn't find a bug in Google even if I spent a couple weeks.
Its interesting how everyone used this as a chance to attack the small modules approach. This approach definitely has downsides, but the problem caused by leftPad being unpublished wasn't one of them.

If jdalton declared a jihad on arrays tomorrow and decided to pull all array related functions from lodash, we would have the exact same problem.

If kriskowal decided that Q must mirror built in Promise and published a version that does this tomorrow, we would again have the exact same problem.

There is only one connection between this problem and the small module approach. As the size of a module decreases, the number of dependencies increases and so does the number of authors that produced your dependencies. With the number of authors increasing, the chances that some author decides to go rouge or protest for some reason also significantly increases.

Therefore, its irresponsible to use this approach with a package manager that allows an old, established module with many dependents to be unpublished so easily by the original author.
In the beginning, every team that is able to build a monolith should also be able to build multiple microservices. Think of microservices being highly cohesive and loosely coupled components...

But this will not scale with respect to the number of dev/ops/qa people or with respect to the number of microservices.
We did it differently from the beginning by starting with four instead of a single team.

Today, we have ~12 "feature teams" and a few teams for "cross cutting concerns": A team that is responsible for loadtests (ensuring scalability), one for (ensuring) security, one for "platform engineering".

The feature teams are responsible for one or few "bounded contexts" (->Domain Driven Design) like "ShoppingCart", "Search", "Navigation". Every BC is implemented by one or more microservices.

Teams have developers, testers, and everything else, that they need to develop and operate their services. Splitting teams by skill (DB, Frontend, ...) instead of splitting by business domain (shopping cart, ...) would only have the effect, that multiple teams heavily depend on each other, all the time. IMHO not a good idea. I would strongly recommend to build mostly independent, autonomous, cross-functional teams. DevOps teams.

--Guido
I agree, the article is equally vague about caffeine. I only intended to link the two, not clear up vagueness :P.
> It should work, but what is it for? For "surveillance", a small drone is far more cost effective.

The article mentions that this aircraft is able to "stay aloft for 5 days". I'm sure no drone has similar loiter capabilities like this craft, not to mention a far higher payload.

Furthermore, I suppose it would be far easier (if not trivial) to turn this vehicle into a drone than an airplane.