skysight-inc/HackerNews huggingface dataset:
Of course, you can also validate XHTML using the provided DTDs if you take out the SGML-specific bits, using a (DTD-)validating XML parser (or indeed use XSLT as you say). But SGML has tag omission/inference, empty elements/HTML "void" elements, attribute short forms, unquoted attributes, Wiki syntaxes/markdown, and other features desired or even required for mere parsing mainstream HTML. As to using XHTML, I'm not sure it has a bright future. Last I've worked with it was like ten years ago (xsl-stylesheet processing instruction etc. on IE6; newer browsers don't seem to support it anymore).

FYI: SGML is way more powerful than XML, and its grammar formalism is identical to that of XML because XML was designed as a simplified subset of SGML. Though Relax NG, and also XML Schema, can theoretically express richer grammars than SGML, they can't be used for HTML due to lack of tag inference and other short syntax features, and the features that Relax NG has over SGML benefit data-oriented rather than document-oriented use cases (eg. the use cases that JSON and other serialization formats are arguably better suited for than markup in the first place IMO).

sgmljs.net can run (also) in the browser, so can also validate HTML5 in the browser.

Disclaimer: my project
Yes I'm sure no FCC would surely mean that wireless spectrum would remain usable.

Apparently the laws of physics are an invention of the state.
> whether bundling of security and UI updates was the way things were going

Clearly, it is...

> and whether giving up control over the update process is acceptable to everyone

Clearly, it's not. But the adoption rates for Windows 10 show that it's acceptable to the vast majority of people.

> by having a very different upgrade regime for Windows 10 Enterprise

Really? How is it "very different".
> I'm adding to each node host a systemd service to create dm-crypt+LVM devices atop of each NVMe drive

That sounds cool; can you describe how you're using systemd for this in a bit more detail? I do this with an Ansible playbook when the machines are provisioned.
There are two separate issues in play here. You're conflating the static/dynamic dimension of language classification with the strongly-/loosely-typed dimension of languages which is what the poster you are responding to was talking about [1]. These two dimensions are orthogonal: languages may be static, but weakly typed (like C), or dynamic but strongly typed (like Python).

I'll allow that there's inevitably some degree of opinion involved here, but I tend to agree with the parent poster that implicit conversion in languages like Javascript, PHP, and Perl is just another vector for bugs, and outweighs any of the advantages you get from having your language coerce everything for you. But then again, i'm one of those people that likes my language to force me to be very explicit about what I mean, so YMMV.

Regardless, the strict equality operator is not at all sufficient to avoid the dangers of JavaScript's implicit conversions. Pretty much _all_ the operators are going to coerce types for you, whether you meant for them to or not. For example, this function:

function increment(i) { return i + 1; }

Adds one to number right? But let’s say you’ve neglected to convert some user input in a form to a number as you should have done elsewhere in your code, and you end up calling increment("1"). This will return "11". So now you potentially have introduced a serious math error into your code you may not notice right away. Conversely, if you did this in Python, the function would have raised a TypeError immediately, because you can’t apply the arithmetic operator to two different types. You can’t just “avoid” type coercion in these loosely-typed languages by understanding the specifics of how it works, because you may not even know it’s happening until you start seeing unexpected results somewhere.

[1] https://en.m.wikipedia.org/wiki/Strong_and_weak_typing
>How could they even consider this bill?

This is the sort of thing the Republicans plan on replacing the ACA with.
For fathers, Cormac McCarthy's The Road.
I am in awe that some people seem only to think about things in terms of how much money can be made. Tech has always had a rich community of sharing. Let's not kill that.
There is another case - where an employee really cares about the company and percieves some risk or problem. If he brings up the issue and it is either ignored or dismissed it causes the employee to become more cynical about the management.
[] + [] === ""

Elegant... hmmmmm
Most Lisp compilers will warn about wrong number of parameters at compile-time. Lisp typically warns at runtime, too.
Thank you for the common sense analogy. I have a 'hunch' that one could whip up a proof based on countably vs uncountably infinite mappings where the number of ways to deceive/offend outweigh the number of authorities which could police them, even assuming such ideals as perfect enforcement and willingness to submit to being policed (i.e. international uniformity of laws). But that's just a first-coffee-of-the-morning hunch.
Yes. I completely switched to message passing functional programming and never looked back.
It's also a lot of fun when someone gets the bright idea of "oh, we'll allocate until we have 75% of RAM and then stop; that will keep us from swapping". Which isn't so terrible until somebody installs a second program using that strategy.
"figure out" - the rest of the first world has implemented this.

Pick a model, deploy, tweak for circumstance.

There's not a learning problem here.
Explaining Tree Shaking in Webpack
Lexicons fascinate me and I often find myself just writing down words that seem to fit together in my mind and doing a little work to create a little ontology with them. Often times I'll find missing concepts and that'll directly lead to an insight about the world. Here's a segment of one I came up with recently before my interest ran out of steam:

identification taxonomy discovery location cultivation collection curation meditation organization workflow analytics design management systems mapping maintenance encapsulation problem-solving incident-clearing derisking

These are all approaches for working with discrete ideas. The thing about context logic is that it's exceedingly and annoyingly heavy. Once you get the hang of it the mind naturally just wants to push the logic to the periphery and go back to doing things the way it used to. If I'm looking to work with an idea, I might look at that list of verbs and ask myself, "what does this idea need?"

There's a converse here of concepts:

philosophy research intelligence marketing sales diplomacy finance development engineering operations health service legal political public-relations celebrity monetary economics business branding creative

At first I was just writing these concepts down, collecting, then suddenly I realized I needed cultivation. So I started just moving them around. Eventually I realized that the former were individual approaches for dealing with ideas and context, while the latter were collective approaches.
> It is as if mathematicians would start with axioms. You do not start with axioms - you start with proofs.

Oh?
I had an autoimmune disease, then the disease had me (2013)
> People who are successful never make these kinds of comments.

I have no idea what qualifies as "successful" to you, but I consider myself modestly successful and I make these kinds of comments. As a mid-level engineer at Google, I make > $200K yearly and own a home in one of the more expensive markets in the country. I'm sure that isn't impressive to millionaires, but it places me in the top 10% of earners and allows me to live quite comfortably.

Yes, I acknowledge that I got to this point with a lot of hard work. I went to a state school in the Midwest. I held part time jobs for the first few years, and for my final years of college I worked a full time job at night and went to school during the day. After graduating I landed a decent job, but pushed myself further by also picking up freelance work on the side. I was very conscious of the gap in skill that I perceived between myself and "real engineers". After a year of this, my skills had improved to the point where I could land a job at a west-coast startup. Luckily for me, this startup had a few big names attached to it that piqued Google's interest: after only 6 months at this startup a Google recruiter contacted me, and I leapt at the chance to interview. It had always been my dream to work at Google, so I took the opportunity seriously. For months, I'd leave work and head to a restaurant nearby to eat and study. I'd order dinner then do coding practice problems in a notebook until the restaurant closed. I'd go home and spend a little time with my fiancée, then after she went to bed I'd type my work into a compiler, fix any issues, then do a few more practice problems, going to bed around 2 or 3. Eventually this lead me to a state where I felt comfortable interviewing, and luckily I did well enough that I received an offer.

The point I'm trying to make with this long-winded story is that I am familiar with hard work, and yet in spite of that I attribute quite a bit of my success to luck. "The victim mentality of blaming the rich" is not something that only poor, lazy people do. Even I feel that inequality is partly a result of those with money and influence pulling the ladder up behind them.
There are sites written entirely in Flash and ActionScript, a platform that is now obsolete. Another attempt was Silverlight and XAML (and JavaScript), dead also. I am not sure the desire to abandon JS is shared by all.
> Why is it "a bad idea" if the loop happens at compile time rather than runtime?

Because you need at least one reliable tool to tell you when there's a problem, and if that tool isn't a compiler, what are you left with? When do you realize that a long compilation is actually in an infinite loop and not simply a long compilation? How do you debug the cause of an infinite compilation?

These questions may have answers, but current compilers aren't designed to address them.
Agreed. Russia appears to have learned a thing or two.

The collapse of the Soviet Union was in some ways an opportunity as it allowed rotting bureaucratic systems to be replaced with more effective ones. It's not like all the expertise and technology went away either.
The name "concept model" is borrowed from one of the papers I cited. The concept model is just "a(x_i,h_{i-1})". It decides what is important. You can sort of think of it like a filter or gate. When the concept model returns a large value, creating a large exponent, the information encoded by "z(x_i,h_{i-1})" dominates the weighted average.
No way.

The poorest people are rural whites and southern/inner city African Americans. The immigrant communities, especially Hispanic immigrants and some asians are harder to assess because they do old school immigrant things like pool resources in the community/extended family and work a lot, but off the books.
Nothing that you said contradicts what I've said, so don't think you're the voice of reason here.

Of course it is good to have browsers supporting more and more features. I'm totally for "the web" against "the native" thing. I hope all "native apps" die in a fire and everything starts being written to run in browsers, as everything gets faster and better.

I just commented about a serious drawback of all this. I don't know what would be a solution, however, or if there's need for a solution.

Of course anyone can if they have domain knowledge and time. Anyone could have built a web browser 50,000 years ago if they had knowledge and time.
WASM will become available on every major browser and there will be ways to backport the code to older browsers (i.e ASM.js or polyfilling). There are also multiple implementations but the community is not split into different ecosystems.

Why do you think this is not possible again?
I really suggest watching these talks for anyone who hasn't. The first especially gets at what kinds of issues javascript has, and what might happen to it.

https://www.destroyallsoftware.com/talks/the-birth-and-death...

https://www.destroyallsoftware.com/talks/wat
If you are operating in a market that hasn't been too distorted by taxes and regulations, there are strong economic incentives to use all resources. Vacant properties are a straight liability, better to rent them out. If the owner is sitting on an unused property waiting for appreciation, they are taking on risk. If everyone already magically knew the future price would be much higher, then current prices would already converge to that amount (discounted to NPV) and the owner could sell now or later.
HN is more about obedience to investors than disobedience. This place is all about corporations, money and warmed-over "tech". It's telling many here are afraid (or unable) to name anyone but a dead man.

Those who engage in more serious activism can name many offhand.
Lastag – tag mp3 files with music genres from last.fm
Adding my two cents :

To some point I can follow the argumentation of the author. However, I do not see any superior alternative to the OO paradigm especially combined with Unit testing. Thus, HN, what are the alternatives to OO ?
Java 9 Process API: The Shape of Things to Come
Google and Levi’s connected smart jacket to come out this fall
One weird trick for turning your HTML/JS website into a smartphone app
I have complained on bsd related threads before how the industry as a whole should be appalled and embarrassed to their core for using core tools, utils like OpenSSH and not giving a damn penny in return to fund its development. Everyone uses OpenSSH. Everyone. It's a core part of almost the entire internet now. The openbsd foundation should be awash in so much cash as to be embarrassed because of it but they are not and I find it absolutely unacceptable, corporate America should be ashamed.
I also subscribe to the opinion that total avoidance of bad things is impossible, and that preparation for handling life's faults is a necessary part of the programming each person should have.
Side question to the main focus but I'm curious, have you found it to be profitable writing a book? Don't need to go into specific numbers but just roughly. It seems that for the amount of time it takes to write a book and the profit made it would work out less hourly than doing contract software work and the value in writing a book is more in self growth. I may be completely wrong though so just wondering from your point of view if you would recommend writing a book to someone else? thanks
ITT: a bunch of people without engineering degrees calling this engineering.

Programming has far more in common with a trade than a profession. Just the process software is developed under should make that very obvious.

Software developers are more like electricians than like electrical engineers.
Employer coupled insurance has certain pathologies. But, I think that insurance as a funding model has is a bigger problem.

"It's a terrible Hobson's choice between affordable health insurance and protecting one's genetic privacy."

Genetics is just another way of getting useful information for pricing insurance efficiently, guessing future medical expenses more accurately. To the extent that pricing becomes efficient it ceases to be insurance. This is basically the case for sick people. Their medical costs are known and high. Price efficiency puts more people in that boat. Known high costs expensive. Known low costs cheap. In an insurance based system, information is priced in.

Insurance is good for costs that are unlikely but high. In medicine, we're looking for a system that caters to all medical scenarios regardless of likelihood. Insurance only makes sense for some.
Just price. $100 for the phone (Moto E) makes it less painful if she loses it. The cost difference between the iPod and the iPhone is a bit steep so the Android phone provides emergency connectivity on the go.
Self plug: https://www.madetech.com/blog/
I initially believed it was a sarcasm!
Building Microservices with Python, Part I
Oh give me a break. People who build things (whether in the physical world or not) are engineers. Anyone who has worked at a serious software company knows it's an engineering profession. A more constructive approach would be to say "hey, here are some things engineers have learned over the years; perhaps some of them would be useful to those who build software for a living?"
Provinces were allowed to override federal criminal law with respect to safe injection sites (federal police in canada were standing outside and arresting addicts as they came in/out)

Note, most local police in canada are federal.

The supreme court ruled that the provincial health concerns overrode federal criminal ones.

https://en.wikipedia.org/wiki/Canada_(AG)_v_PHS_Community_Se...

This sort of thing has a long history in Canada. Although in theory the federal government is much stronger than the USA federal government with respect to Provinces/States, the reality has played out significantly differently. Likely because of the influence of Quebec on canadian regional politics, and the fact there are fewer provinces than there are American states.
I think we actually agree on the need for regulation. I just don't think being subject to regulation is necessary to be considered an "engineer".
Show HN: Publish npm package in beta tag with version automatically increased
The DMCA has incentivized everything we see our current corporate-dictated web environment by making none of these businesses liable for any of their actions. The spread of misinformation is a kind of emergent phenomenon.

The democratic nature of physical reality hasn't led to every publication turning into the National Enquirer.
http://semiengineering.com/ as I think we are at an inflection point of Moore's Law and it is worth understanding how that plays out at the lower layers of the stack.
Thanks! Confusing because I think "bitrate" when I hear "compression" but it actually refers to the volume level.
My favourite these days is Linux OOM killer. For some people it's just right to randomly kill a process instead of rejecting the current request. My mind gets a blue-screen every time I'm contemplating this issu.,....ds.fsd... :)

edit: https://discuss.96boards.org/t/yocto/576
Corporate and elite interests get away with this because of the propaganda of 'American exceptionalism' - people are brainwashed into thinking that we have it so much better that other countries, so don't complain. The news media is a powerful tool of control. Not watching any news at all on TV would yield a more accurate world view, that is, the news is a negative information source.
The term "engineer" is regulated in Canada, and only Professional Engineers (PE) awarded a licence by their provincial regulatory body can call themselves as such. Someone who graduates with an engineering degree is usually called an Engineer in Training (EIT), until they become a PE. The reason we regulate a specific word for our profession is because of our relationship with the public, and the ethical and safety promises engineers are regulated to commit to the them. The average person does not have the technical background to judge the proficiency of an engineer, so they must trust in their abilities and morals. In Canada, engineering is a self regulated profession designed to uphold high technical and ethical standards so that we can maintain that trust society gives us. The intention is, that when someone calls them self an engineer, you can have confidence in both their technical ability and moral obligations. To be effective, the standards of the term and definition of who can and can't use it needs to be regulated.

That being said, I normally refer to myself as a chemical engineer (not a chemical EIT). I think the distinction needs to be made when you're interacting with someone that you are offering your engineering services to. For example, when at work I would always sign my emails indicating that I was an EIT.
Spend some time in Russia (outside of the nice parts of the big cities) and you might understand what I mean.

I do actually think that the diminishing quality of life there constitutes a threat to support for their government, including its intel services.

Just my opinion, but one based on lived experience.
They don't understand the actual technical details -- what the word "block chain" means, which then allows them to grammatically abuse the word and even conjoin it (they're journalists).

https://en.m.wikipedia.org/wiki/Blockchain
Not really:

http://physics.stackexchange.com/questions/59929/what-preven...
Land of the free. It's the free market and all that bullshit that USA like to get proud of. Now people is going to be a nice resource and a cheap and easily replaceable one too.
The O'Reilly blog was unknown to me until today. On first glance, it seems that they have lots of interesting articles in my areas of interest (ML, data science, data governance).

Thanks for the tip!
People sometimes think that OOP means "OOP or Nothing!" probably because of the popularity of languages that enforce such a mentality (i.e. basically because Java).
I started programming before OOP was widely adopted (C++ was available on some platforms but costly). The C code we worked on wasn't structured very rigorously. There were really no rules or guidelines. I worked on telecommunications software, compilers, and databases.

C structs were used obviously to hold data. Structs were created after analyzing the data to be stored, determining multiplicities, lifetime, etc.

C functions were frequently large and handled numerous concerns. Programmers usually started with one function and split off other functions as needed mostly to take advantage of commonality and to avoid deep nesting.
I agree with your initial sentiments, but your fianancial advice has me wondering how old you are.

If you're not old enough to live through what happened in 2001/2008 then you have some serious blind spots.

And I don't mean just alive in 2001/2008, I mean riding high on your investment choices thinking you're a genius only to have everything come crashing down.

When things come crashing down again (and they will) you won't pull your money out because you'll think it's just a dip on the way back up.

If you're young enough, that's all you know, small dips that rise to new heights.

If you're older, you've seen dips that go back up, then dip lower, then go back up, and lower, etc... and each step of the way you think, don't sell now it's going to go back up. That later turns into, don't sell now or I'll lose money.

And finally, you've ridden it all the way to the bottom with no cash. Let's hope in this down turn that you still have a job.

Sorry, if that sounds a bit dark, but I've seen this before and you should be careful with how you invest your money. Cash or equivalents should be a component of your portfolio.

I keep a few years of expenses in cash equivalents. Once you achieve that you become immune to market swings and job turnover.
IS IT a SCAM? Download PLR Products Review – Find Out NOW
Do the first 50 problems on projecteuler. they're fairly easy (compared to the other problems). it'll take you a day or two. or maybe a week, if you're really weak at that kind of thing. afterwards, you will ace all the stupid online tests.
How to flirt for toddlers
This whole line of reasoning that Psychopath = Super Intelligence Serial Killer is misguided.

All of the studies to date have used the criminal population as the sole source of research for psychopathy - as your reference does.

The point I was making with my lengthy post is that, in fact, genius level psychopaths don't become murderers; they become Presidents, Dictators and Hedge Fund managers.
Started programming in 1982. Object oriented programming was a huge advance - especially in developer productivity. A side effect was the dramatic improvement in developer tools: gui builders, IDEs, etc all improved dramatically. Probably the watershed moment for OO was this NeXT video that showed the difference: https://www.youtube.com/watch?v=UGhfB-NICzg