skysight-inc/HackerNews huggingface dataset:
For those of us coming from non-Linux systems (and I'm speaking for illumos/SmartOS here), the effort required to debug the kernel displayed here is galling. That this is so difficult reflects Torvalds' historic disposition against kernel developers[1]:

I don't like debuggers. Never have, probably never will. I use gdb all the
time, but I tend to use it not as a debugger, but as a disassembler on
steroids that you can program.

None of the arguments for a kernel debugger has touched me in the least.
And trust me, over the years I've heard quite a lot of them. In the end,
they tend to boil down to basically:

- it would be so much easier to do development, and we'd be able to add
new things faster.

And quite frankly, I don't care. I don't think kernel development should
be "easy". I do not condone single-stepping through code to find the bug.
I do not think that extra visibility into the system is necessarily a good
thing.

To be fair, this was a long time ago (17 years ago!), but the experience relayed here leaves one believing that Torvalds' historic attitude has cast a long shadow.

And if it needs to be said, Torvalds' arguments are themselves deeply confused; he has conflated single-step in situ debugging (which does in fact suffer from limited utility in the context of an OS kernel) with debugging writ large. So as he rejected in situ debugging, he also implicitly rejected postmortem debugging and dynamic instrumentation -- both of which have proved absolutely essential for kernel development. (Indeed, it is likely that DTrace alone would have allowed the author to debug their problem, as its design center is exactly the kind of non-fatal failure described.)

The tutorial will certainly save others pain, but that such pain still exists at all in Linux is deeply unfortunate, and a vivid example of Linux not representing anything close to the state-of-the-art in systems development.

[1] https://lwn.net/2000/0914/a/lt-debugger.php3
Depends on how much the hashrate changed: http://bitcoinandtheblockchain.blogspot.com/2017/08/chain-de...
Short term betting (for or against) Bitcoin is unlikely to result in much profit.
Might want to consider moving the homepage to Github pages
I'm not, and I don't think most other people are, advocating for total equality. There has to be democratic push-back against the drive towards massive accumulation in capitalism or you don't get to have functional capitalism. It's a catch 22. Without some non-capitalist institution with a lever of power to redistribute, capitalism has a built in tendency towards self-destruction.

Workers can't afford to buy the products and businesses lose demand in a downward spiral.

That's what worked about the New Deal. If capitalist's want to continue getting to be capitalists, they have to sacrifice large amounts of profit to the common good. They still get to be wealthier than every one else, just by a smaller amount.

I really just consider life extension a wealthy vanity project. All of them contribute some money to defeating death, just in case...It really makes you think you should be in the business of promising immortality to wealthy people.
> This thing lets you understand the performance cost of npm install ing a new npm package before actually adding it to your bundle.

Unless you are specifically concerned about the `npm install` performance in node, in which case the npm package size is relevant, you never include the whole NPM package in your bundle. Most universal packages include separate dist files and separate entry points for node usage, so most of the content is actually not included.

If you are truly interested in bloat, let your bundler give you a summary at the end. Webpack can give you detailed information about what files were included, how much each file costs, and why the costs were incurred.
Setup from yesterday:

We are at a restaurant in Manhattan. Place is reasonably priced by Manhattan standards (i.e. overpriced for 99.9% eveywhere else) but it delivers value - a very decent brunch for 2 people with a 2 glasses of wine + tip $80.

Behind us there's a table of 3 people. They are debating if they want to order another glass of wine and basically tip nearly nothing to the waiter or if they tip to the waiter the customary 20% and go home: they dont have the money to do another round and tip.

Kicker: for last twenty minutes they were talking how all of them on Friday invested into bitcoin and how they are going to be rich.

This is the current bitcoin investor.
I avoid animal products so can't say.
Wirecast Pro 8.2.0 Full Crack and Serial Key Free Download
Make isn't hierarchical and your build system probably doesn't need to be either. IMO ini/TOML format would be the way to go.
Modern stovetop pressure cookers are pretty safe these days but some people certainly worry and, as others have said, they can be a bit fiddly. You certainly don't fire them up and leave the house.

Influencer marketing is a big deal in many product categories these days. The details vary by B2B or B2C, product/service area, etc. But reviews by people who may not be full-time writers and reviewers can be very important, especially for product categories that don't have a lot of trusted expert review sources.

With money and goods often changing hands there can be a whiff of payola about the whole process. But most people who have a trusted following really are giving honest opinions. You may be able to get me to write a review if you send me something I'm interested and qualified to have an opinion on. I'm not going to be positive just because because I got some freebie though.
> I think if one truly took this approach to the logical end, they would end up creating their own specialized board game programming language.

That's what I was planning on saying. A set of discrete rules detailed enough to represent most board games would end up looking a lot like an interpreted programming language.
This is a great critique of a coding style, but not really a language. Being an older person, I can appreciate how much object oriented languages helped organize complex code. But then it became a religion and we got the silliness the author describe. Keep in mind, no matter how smart you are, something you are doing today is going to seem really dumb twenty years from now.
Indeed it's almost trivial. I wrote a similar tool that is also able to split chunks of work between different machines: https://github.com/dullgiulio/empa/tree/master/cmd/ep

But again, no IPC, just a simplified "GNU Parallel."
A content-based web doesn't solve discovering content.
C# often has "release valves" that allow you to divert from some of the mess that Java tends to exhibit. `events` and `delegates` from C# 1/.NET 1, flawed as they may be in retrospect, alone simplify several major patterns that Java falls into.

I also think on the paradigm issue here is Java architects seem more inclined to have a "ravioli code" problem. There's an ancient Java ideal of componentization [1] that a lot of Java code tries to live up to. Lots of little components boxed into tight containers that only ever interact through often "reconfigurable" sauce: ravioli.

There are some benefits to that ideal, it exists because it has some merits in terms of component testing, in particular. It's just that as with spaghetti code and copypasta code, ravioli code also sometimes winds up in a mess where the ideal meets the real world, and somehow a toddler (or junior developer in this analogy?) has thrown it all over the kitchen and you have no idea how to clean it up without destroying the entire kitchen and starting over... May not be a great analogy. ;)

I'd argue that you are more likely to see Java-style ravioli code in C# projects that use IoC containers of one sort or another. Again, there's nothing particularly wrong with IoC containers [2] as an idea connected to some ideals of component testing, it's just that it's an ideal that often falls down and fails to deliver its advantages in the real world.

[1] That somewhat resembles the Smalltalk ideal of object message passing while the language itself lacks much of the architecture for that. Arguably, a lot of Java's worst problems come from trying to replicate a lot of Smalltalk ideas and design patterns in a language that is nothing at all like Smalltalk and misses some important characteristics of Smalltalk.

[2] IoC Containers are a ravioli concept directly imported to C# from the Java world, with the earliest IoC containers such as Spring.NET being Java ports.
It is not "shitting" on any language to point out that there are many tools and using the right tool for the job at hand is the way to go.

> a lot of performance critical things need to happen in the web environment

Can you provide a single example of a real world web app that uses manual memory management as described in this article?
That's pretty funny, but EventFactoryFactoryFactory isn't exactly Java's fault.

There's a software development culture that believes adding a layer of abstraction is the answer (doesn't matter what the problem is) as long as it has a GoF pattern name (doesn't even need the implement the pattern its named for).

For whatever reason they've adopted Java, but if you're going to throw abstractions on top of abstractions carelessly you're going to create a mess of spaghetti no matter the language or environment.

(I think the preference for Java is just an accident of timing of when the culture arose. The responsibilities of corporate IT groups were exploding and they needed a language for all the software they had to create. Java was there and it was a good choice.)

I'm feeling bad about my laughing and complaining, which is useless, so here's some practical advice on restraint when it comes to using abstractions and patterns:

* Don't use an abstraction to wrap something you don't understand well. You may feel like you've tamed a confusing, complicated API and turned it into something you do understand and can use effectively. But you've actually just rolled up all the things to didn't account for and don't understand and hidden them away from view where they will explode if your software actually sees much use. I realize this isn't always easy to avoid doing, but at least never wrap something in an abstraction because you don't understand it that well. And when you're forced to implement an abstraction on top of an API you don't understand well, go through the API, method (or function or endpoint or whatever) by method, and look at all the options and ask yourself what each of those options and methods are there for.

* When considering using a pattern, make sure to check the section titled something like "When Does This Pattern Apply?" and make sure the abstraction you're considering actually solves the problem.
Do people not carry cash?

Maybe the types who have an apartment with a doorman in Manhattan don't. But I (a "millenial") often go to bars and restaurants that are cash only.

Eventually, I found it was easier keep budget my "entertainment" in cash. Visually being able to see how much I have, how much I'm taking out helps. Being able to see that amount grow if I'm frugal one month feels good too.

I have friends who claim they get value from "points". But unless you're working towards a spending minimum for a sign up bonus, I've found the amount you make (2-5%) from using your credit card is less than the savings from thinking critically about which cash purchases to make.
Our max may be higher but I too would like to see that our average is higher because I rarely get the speeds I pay for.
Bitcoin.com founder has sold all his Bitcoins because it's “as good as useless”
* Your attitude is the exact opposite. *

You setting your theory against my lived experience. If you want to understand the situation more fully, you can read How To Destroy A Tech Startup In Three Easy Steps:

https://www.amazon.com/Destroy-Tech-Startup-Easy-Steps/dp/09...

I did my best to re-create the extent to which decisions were driven by panic and the pressure of time.

Please note, every company in the world has a finite amount of time, and a finite amount of money. You can argue that a company should hire people with more experience, but people with more experience will be more expensive, so you will end up with less people. Or you can argue that a company should hire more people, of less experience, and then train them. Training takes time, so in this case you are trading time for money.

All of these strategies work, but in different circumstances. In the circumstances that I faced in 2015, described in the book, I advocated for the strategy of less people, of a higher skill level. I was, however, outvoted, which is a reality of corporate life.

It is relatively rare that a company follows an ideal strategy. What I see instead is constant course correction, often with a bit of a lag, so that the company ends up having the ideal strategy for dealing with the situation that it faced 6 months ago, which is not necessarily the ideal strategy for what it is facing now.

Business tends to be chaotic. The Platonic Ideal of computer programming needs to be adjust to the real realities that businesses face.

To be clear, Sital's attitude was a major problem, and myself and co-workers advocated that he be fired. But management kept him on, and I was given the responsibility of covering for the gaps in his knowledge. I was not happy about this, but this is a reality of business: we often have to accept that a decision has been made that we strongly disagree with, and then we need to somehow make the best of it.
San Francisco's First Personal Electric Mobility Sharing Platform
I wanted to keep the UI from getting too busy, which is why I limited the degree to 7. But if somebody really wants to play with higher-degree polynomials, I'm not going to stop them!
My wife and I both had insurance when our son was born-- and gold plated insurance, at that. I still went back and forth with the hospital for over a year arguing about bills, until they sent us to collections, even though they owed us $800 for overpayment. I had to threaten to take them to court before it was resolved. Our son was walking, and they still hadn't figured out how to bill us for it.

I'm still not 100% sure they aren't going to resurrect those bills in another 6 months.
Since some folks are still looking at this, I'll note that a successful SF book from a major publisher may only sell 30-40k copies over its lifespan. I believe it's Prime Palaver #6 where Eric Flint discusses some of this in relation to Baen's Free Library.

With numbers like that, it's not hard to believe that a little-known author may only sell a few thousand copies, many of them to dedicated followers.
Seriously you don't keep any cash for emergencies small payments and so on?
I’m saying that even if we don’t have reciprocity, if the drug is separately approved in both countries, it should be legal to buy in Canada and take to the US.
And this is important because the author misses the point as to why people get value from the "middlemen" -- to find stuff. Even with a content-centered web, there will be a need to find content and people, and new discovery engines and aggregators will emerge.
These are all good points except for the idea that it won't be used like normal money. The speculative environment and price volatility resulting from that, is all by design. The mining incentive creates a "boom" environment to help bootstrap the currency.

Now, a few years later, BTC is blessed by regulators. The next phase of world domination is for the governance model of Bitcoin to start to seem far better than fiat governance models. This is just a matter of time.
It is not so much a directional play as it is a force for arbitrage opportunities.
I wouldn't say "anyone" is trying to hard but I have seen a lot of people who immediately disregard guis as soon as they internalize that the cli is more difficult. Reasons include wanting to be "badass" or "smart". Yet many also do not care about how got differs and basically ask "how do I save" and proceed to revolve their entire workflow on a few copy pasted or memorized commands.other they hear how "rebase" is only for "smart" people...

On the opposite side gui users can often be unaware of the actual model and instead be working with imperfect internal models with be GUI being a crutch.

In both cases there is lack of desire to learn but I'm often more sympathetic to the latter where people want just enough information to do their work well as oppossed to the former who often make things harder than they have to be in all areas and have lost touch with true expertise in favor of appearance of expertise.
And Standard Oil, Alcoa and Carnegie Steel/U.S. Steel demonstrate how lack of government regulations establish monopolies and cronyism...
You almost never checkout to a commit. You checkout to a branch. A branch is a reference to a commit, and the HEAD is a reference to a branch. The HEAD is where you are right now. When you make the HEAD point to a specific commit, you're in a 'detached head' state.

`git log` tells you all the commits that are part of the branch. More generally, they are the commits who are children of the current commit (the commit your branch points to).

`git reflog` tells you where your HEAD has been. When you change for branch to branch, the HEAD moves around. That history is recorded in the reflog. If you botch a rebase, your HEAD will sit on top of the newly created (and botched) commits. You can still access your previous commit by looking where the HEAD was before moving to the new commits made by the rebase.
AUS Students Develop Device to Reduce Car Mishaps
Awesome! I need to update that article for the changes in Phoenix 1.3 but for the most part everything in there should be consistent.
The real problem with npm and JavaScript is not the package manager, it is the lack of a standard library bundled with the runtime that has such basic functions. To someone coming to JavaScript from a Java/C# world, the fact that a package like isArray actually exists, nevermind the ridiculous number of downloads it has, is mind boggling. Using a dependency like this on a Java project will get you crucified in any sane team.

If you want to get out of this dependency hell, bundle these small, essential functions into the runtime.
For a robotics focus, ICRA and IROS are the big ones. IMHO ICRA is a bit bigger and better than IROS but it's close.

Robotics: Science and Systems (RSS) is smaller but its paper acceptance is much more selective and it is becoming a very prestigious conference. It's also single-track, which makes it nice as an attendee (ICRA and IROS run probably eight to ten parallel tracks).
I think people write bad makefiles because the documentation is bad. Its "taking the user by the hand and pushing him into the right direction"-level is just not up to date anymore.

Make is a good tool because it allows a lot of flexibility, but it doesn't protect its users from the pitfalls this flexibility unavoidably creates.
Many of the people we're talking about were dumb enough to buy $500k+ homes on "stated income loans", when they had little or no actual income to speak of. While I do think the people who were offering those loans should have been punished both financially and criminally, I don't think the people who were foolish enough to use them to buy homes they couldn't afford should have been rewarded.
I dont think there are any experienced shorters sane enough to short something with this much upward momentum. Once we get a decent downtrend though watch out.
3) That's not true. I'm using their Android app and marking any mail read/unread is instantly replicated to the open web interface on my desktop machine and vice versa.
A friend's rural internet connection was getting 50kb throughput recently. It turned out the line was lying across an electric fence. Clearing it got him back up to his usual 1mb
A concierge at a 5* hotel can make bank - need a source for those Hamilton tickets for example
https://www.ripmedicaldebt.org/
True, but those arbitrage opportunities will stabilize the price and make other similar opportunities less profitable. I suspect that the real reason these haven't all been ironed out
(exploited already) is because Bitcoin exchanges lack the infrastructure guarantee that transactions close when they are expected to, and thus the fee levels wash out much of the arbitrage (for now). But arbitrageurs operating outside the exchanges can use this to their advantage and probably harvest a bit of profit on the chaos for the time being.
This article is valuable since it's raising some interesting pitfalls it's good to know and avoid.

That being said: you need to use the right tool for the job.

It's just hilarious how people expect the new "foo framework/paradigm" to solve ALL the problems... jeez! It's nice to know and understand new paradigms, but you really need to evaluate your case.

ORMs took away the complexity of 90% of web apps. All the "Model X has many model Y". If you step outside of that realm with the ORM then you're officially "fighting the framework", and bad things will happen.
That is so incredibly true that you only have to explain it to people like anarchists who wish it weren't. By their logic men everywhere would have lost their sex drive the minute women got the pill.

There are just so many examples of predictable human irrationality attributable to this that it's hard to believe anyone doesn't understand it.

We keep executing our adaptations thousands of years after they cease to be useful.
FWIW, if you create a GKE cluster and create an nginx deployment:

kubectl apply -f https://k8s.io/docs/tasks/run-application/deployment.yaml

And simply create a Load Balancer:

https://kubernetes.io/docs/tasks/access-application-cluster/...

You have nginx exposed via an external IP address in about two minutes. Once you're comfortable with that, you can start working in Ingress and such to get more sophisticated.

I agree the IRC/Slack channel communication isn't the best. I prefer the Kubernetes User Group. You can usually get a great response in less than a day. I've used it a lot.
Show HN: Dependabot – Automated Dependency Update PRs for Ruby, JS, Python and PHP
Hey there. I'm a personality type enthusiast and would be interested to chat about some of these things. If you're up for it, send me a note to: trolochecr@hs130.com
Those prices are a bit high for typical UK season tickets. 85 miles Poughkeepsie to NY 90 minutes, similar distance + time and number of trains per day to Salisbury to London (88 miles). A weekly season there (so 10 trips) will set you back £131, or $175, 20c/mile, half the price of Poughkeepsie to New York.
My ability to choose whether to tip less for bad service is a way to encourage servers to give good service.

My experience traveling is that places like France with legally mandated tip amounts have very inconsistent service quality. It can be good, but it can also be very bad. And when a server decides to make your service bad, there is nothing that you can really do about it and nobody will care.
Your example doesn’t account for substitutes, though. Before commercial flights, civilians couldn’t fly. Before Hybridizer, programmers could still use CUDA.
If you are short and bitcoin goes up, then you should lose money. That is expected.

If bitcoin price crashes, how does it imply exchanges will become compromised???

Counterparty risk also exists for established exchanges. Secondly I’d venture to say for retail traders, their offerings are vastly inferior to bitfinex/bitmex/okcoin. You get much higher leverage and lower margin requirements. You also don’t pay for quotes or any “access” fees which eat into your margins.