skysight-inc/HackerNews huggingface dataset:
Web page rendering is far from similar on different browsers. I agreed that an alternative to PDF would be a good thing, but it probably would be more like a lightweight
PDF than what HTML is today.
I've been using unison lately. Nice and quick over 1000s of files between OSX and Linux. A little slower when paired with Windows though
I found this out the hard way a month ago when I updated my hackintosh from 10.13 to 10.14.

Never assume, even several weeks after a macOS release, that working Nvidia drivers will be available!
Prices being too high to begin with.

It doesn't matter how useful crypto is (marginally, so far) or how much the underlying infrastructure has improved in the last year (a lot). If prices are rising at 10% per day for a couple months - which is what they were doing last December - then it's basically guaranteed that they're going to get ahead of fundamental value. Realistically, the only way out of this situation is for prices to fall by a lot, which is exactly what's been happening over the last year.

Bitcoin has the same price now that it had in August 2017. It's actually done about as well as the S&P 500 since June 2017, and a fair bit better since Trump's inauguration (it's up about 300% since January 2017, while the S&P 500 is up about 20%). It's just that in the middle of that time period it had this huge bubble, which just happens to be when most people heard about it and bought in, so the median crypto investor is now down about 80%.
I'm pretty sure OP is saying, "Hey, tech companies, if you're going to mine my data to figure out I'm pregnant, maybe you should give me some way to tell you that the pregnancy ended in sorrow, and I don't want to see any ads about baby needs."

It's not calling for a ban on baby product ads.

It's saying that force-feeding ads on baby products to someone who has lost their child is awful, and it doesn't seem like a big stretch to let a user say, "I don't have a baby!" in a way that tech companies / advertisers can use, to be more sensitive.
Azure. Microsoft revolves around Azure these days, if they can provide a better dev experience that leads to more people using Azure they're happy to spend money on it.
I always find this comment funny, because C++ is older than Java and many Java programming patterns originated from C++ designs.

Then again, many C++ younger devs don't even know what Booch method might be all about.
A server can do way more.
Steve Jobs even felt threatened enough by looking glass to call Jonathan Schwartz (Sun's CEO) and tried to intimidate him: https://jonathanischwartz.wordpress.com/2010/03/09/good-arti...
F# doesn't support any of those features you listed. If you want ad-hoc polymorphism there are a few hacks available: https://withouttheloop.com/articles/2014-10-21-fsharp-adhoc-...
At the risk of derailing things and spiraling into off-topic chatter... is anyone else really bothered by the background music on the Freakonomics podcast? They seem to use the same tracks every episode. Ten years ago that wasn't particularly grating, but as production values in podcasting have gone up listening now I feel like I'm hearing a marketing video thrown together on fiverr.
You almost make it sound like a bad thing.
Git Tip: List the Most Recent Branches You Are Working On
MobSF – Android Security Analysis Tools
Learn to code (or do anything): top down, bottom up and other approaches
Not this again! David Mozer’s article has been posted to death here and debated to all end. It’s mostly correct but deeply sensationalized to the point where I believe it’s more damaging than useful for those who haven’t studied character based languages.
> Ah, references "fuzzy logic". That was one system that really needed to go away.

AFAIK, fuzzy logic, and application in fuzzy control systems among other areas, is still a very active thing.
I think exceptions are kind of cursed by their name. To treat exceptions correctly you have to constantly keep in mind that they are misnamed. And you have to deal with type systems that do not treat them as precisely as they treat return values. And on top of that you have to coexist with people who impose all kinds of semantic limitations on their mental model of exceptions, such as that they have to be "exceptional." Exceptions have to be treated as happening all the time, and in strongly typed languages (such as Scala, my hammer) you have to keep in mind that the type system has this huge loophole built in that is very important and that the type system gives you very little help with.

(The most obvious example that utterly confounds semantic limitations on exceptions is opening a file. Programmers accustomed to working on a certain kind of system find it quite natural to regard a missing file as "exceptional", even fatal — for them a missing file means the install or even the very build is corrupted. Programmers who work on a different kind of software may regard missing files as completely routine, maybe a commonplace result of user error. If these two groups of programmers believe exceptions are "exceptional" they will never agree on the contract for opening a file. Another example is deciding whether something that happens 0.0001% of the time is exceptional. Some programmers will regard that as exceptional while others will consider it utterly routine and regard it as a failure of discipline to believe otherwise.)

(The logical consequence of insisting on "exceptionality" is that you need two sets of basic libraries for everything and may need to mass refactor your code from one to the other as your use cases change. This is a needless imposition that offers no recompense for its offensiveness to good taste and good sense.)

The great merit of exceptions is that they remove boilerplate and make it trivial (nothing is more trivial and readable than no code) to express "I am not handling this, someone else must" which makes it quite easy to e.g. signal "400 Bad Request" from deep within some code that parses a request entity.

Personally, I think that for now it is best to prefer exceptions for writing lots of useful code quickly and concisely and to prefer strongly-typed, expressively-typed return values for achieving a higher level of care and reliability. But I look forward to a better linguistic solution that combines the virtues of both these approaches — and I have to admit that in my ignorance of many important languages I may be overlooking an already existing solution. I am reminded that in the early 2000s I would have relegated all static typing to the "verbose boring highest reliability required" category and then type inference and other ergonomic advances converted me to statically typed languages such as Scala as the best way to pump out lots of valuable working code. I'm looking forward to a linguistic solution to this problem.
Deepnote – the easiest way to run Jupyter notebooks
You should spend 30 minutes talking with a project coordinator for any construction job and you'll change your mind.

My company recently opened its first retail store in a new Caruso mall, and it was a considerably eye-opening experience. The pace (and cost) is frustrating, but the end result is generally fantastic and that's more than I can say for most software projects.

Even for a simple job, the number of things that need to align to allow for a dump truck to deliver gravel to a construction site is non-trivial. Along with permits and what times the truck can arrive depending on whatever bureaucratic bullshit is at play, you also need to make sure the rest of the crew is in place to receive the delivery and put it to use. Don't forget about the things that need to be done even before the gravel can be delivered, and things dependent on the delivery that begin on that task is complete.

This isn't a software project. A simple truck delivery being late can require dozens of people to get involved to reschedule everything else that needed to come after it - this is non-trivial, expensive, and can impact hundreds of people depending on how much the schedule slips since we often dealing with hourly labor.

"But it's only changing one delivery" you say? The delivery was probably handled by a contractor, which has other clients and other responsibilities and may not be able to reschedule when it's convenient for you. Multiply this by every contractor or 3rd party you're working with and suddenly Metcalfe's law is punching you in the face.

The waterfall approach exists because it works - on average - considerably better than everything else that's been tried before it, regardless of whatever cosmic forces we think are at play.
Canada absolutely should not have considered it when deciding to get involved.

Canada, like any civilized nation, should follow the rule of law. If that has consequences for our deals with and nationals living in totalitarian states, so be it. You shouldn't get to be above the law just because a big trading partner wants you to be.

Canada doesn't have a president, but the idea that our Prime Minister, or more importantly, our government respects the rule of law more than China isn't a hard sell at all. As bad as Trump is, the same is true about him (even if arguably only because the system forces it on him), and is certainly true of the American government as a whole.
The college student would be regarded as pretentious because they can't follow through with the expectations set by that sentence. They haven't developed a mastery of all the techniques and an intuition around using/abusing rules to enhance the reader's experience. A student could create that sentence, but they could not create the story.
For me it's about code clutter or cognitive load.

curly braces or semicolons do not serve a purpose most of the time.

as F# is a functional language you do not require them to seperate statements as you always pass values...I hope you know what I mean.
Ah Royal Noir! I remember those days, my friends were pimping their bikes and I was pimping my desktop. I had to find Royal Noir on the internet because it wasn't embedded with XP, and with each download, one virus gift :D
The fact that companies still have the email-> employee pc -> acrobat reader pipeline enabled says a lot about what companies really think about security, posturing aside.

(home users too, but they can plead ignorance)
> None of this 'How China Works' is new to anyone. Canada should have considered it when deciding to get involved.

Maybe on HN, but is this really old news to all of our governments? I was watching CBC last night on all the issues the Canadian government is now running into with their 5g rollout since they were one of the few western countries who decided to deal with china.

Either they didn't know what china was, or they have better information on china then we do.

> And our president respecting rule of law or being better than Xi on any measure except successful criminal behavior is a real tough sell.

Is this a troll? Did we see trump pass a law unlocking the term limit for president? Because Xi did that, that's why hes even still in office.
I've done exactly that. Mark my words, a PDF will be the first computer program to gain full sentience.
If I use a garbage collector in an assembly language program, then I get pauses; the assembly language is still "close to the metal".

There are ways to avoid garbage collection pauses in Lisp or minimize them ranging from program design and coding techniques, as well as compiler optimizations to avoid the consing that leads to garbage collection, to garbage collectors that perform incrementally so as to conceal the pauses by amortization over time.

Lisp was implemented on IBM mainframes initially and then various other mainstream hardware. Research on Lisp-oriented hardware began in 1973 or so, and wasn't commercialized until 1979 or so; the "boom" in Lisp machines could be regarded as a 1980's phenomenon.

Lisp machines allow for type checking to be significantly reduced in cost. The hardware instructions themselves can perform a check such as whether the two operands to an add instruction are integers. A Lisp machine can have idealized type representations as well, so that Lisp programs aren't disadvantaged on it. E.g. It's hard to stick a type tag into floating-point numbers on conventional hardware (doing so involves a loss of mantissa bits), but we could design Lisp hardware which has it has type bits as part of the floating representation.

Run-time type checking overhead can also be reduced in compiled Lisp programs on conventional machines thanks to type information which is either inferred to some extent, or comes from declarations, or a combination of both.
Conky is great. For someone starting out in customising their desktop, Conky goes a long way. I used it for years till I started writing my own widgets.

I was using Conky for a todo list on my second monitor, then I added another more specific todo list called "weekdo", one for notes(like how to spell certain words that consistently stymie me). After growing to four lists, each a Conky instance, I wrote a more specific purpose displayer. That was worse on resources, but a rewrite incorporating all the lists into one process was an improvement, even on Conky.

But this is about Conky. Conky pretties up your desktop, displays useful information, and inspires you to take more control of your desktop. Long live Conky.
It's got a 3d model viewer in it
Well, at least _some_ aspects of a 50k feet Waterfall are not avoidable in any construction project, as you can‘t redo parts of the foundation when you‘re building the 50th floor.

Something that works quite in the same way (not as strongly, but still significantly so) in software by the way is re-modelling of the underlying entity schema.

Which by the way is my favorite beef with process-driven agile methods and why I‘m leading my projects with an initial phase of data model and UX sessions until it‘s exactly clear _what_ needs to be built and _how_. Only then does it make sense to build any working code IMHO.

Scrum and friends come with a complete disregard for distinguishing the stuff that‘s easy to change later on vs. the parts that are not.
Well, he is the God of Mischief (in the Marvelverse anyway).
Yep. Underestimating frontend complexity is how we got into this mess. Say what you will about framework churn, React is the first one where I really feel like it's easy to apply basic coding hygiene (e.g. treating abstraction and composition as first-order concerns).
One of the specific claims was that a robot intended for packaging lithium cells into battery modules misbehaved and punctured the battery module casings, damaging some of the cells. He alleges that Tesla then simply fixed the robot, and sent dangerously damaged battery modules to be integrated not vehicles. He published a list of Model 3 VINs which he alleges have the dangerous matters modules installed.

There are other claims about unsafe storage of hazardous waste, but that battery module claim is the one that sticks in my memory.
As I understand it, F#'s async funktionality was there first, and C# TPL was modeled after it, but I might be mistaken...

Anyhow I am with you that this is one of the problems I have with F#. Interop from F# to C# is generally pretty bad.
Agreed. I like to tell people that I like Redux's devtools more than I like Redux. There's a payoff for all the boilerplate.
Does NVIDIA actually have a contract with Apple? I was under the impression that Apple silently tolerated them, and that they just released drivers on their website for eGPUs.
When we deal with state full objects (classes instances/ database objects/ in memory caches) -- we have to segregate the operations on those objects as:

( 1 )
Operation can be applied multiple times -- result will not change (idempotant op) -- eg delete, select

( 2 )
Operation order is important (eg balance cannot increment before payment is processed )

( 3 ) operation order is not important, or ordering conflicts can be mitigated by the solution/underlying platform completely.

So what React team has realized, is that updating a state variable ( a change operation), often falls into ( 2 ).

As react getting more and more use, it tries to find more and more areas to optimize. Which is good.

In both time and ram-space dimensions...

For the React's run-time system, to perform global optimizations, it is really important to know what order the developer had implied in his/her design for case ( 2 ).

Very similar, to what an optmizing compiler, would like to know about a flow of calls/etc.

this is very difficult to do for a user level application in JS.

Without some help from the developer using the library, those optimizations cannot be done, or they will cause user's state to get corrupted.

Their solution is to keep the existing machinery as is, but allow a user to 'tell' the framework about the state variables a bit more than usual.

To me this this a fair tradeoff/ask.

So I will have to learn a bit more, and may be even restructure my code, to let React (and React Native) to do better global optimizations....

Why not ?!

Most programming languages syntax is poor as specifying the intended order of function invocation or value change rules, as 'compile-time' directive.
(well, I at least, do not know of any language that let's me do that -- so I resort to forcing some order though function arguments and return type, so that a call to nxt function, must have a certain type provided by a return of a previous function...

I think explicit state management, is absolutely the correct problem to tackle. it is difficult and error prone.

It is not fair, in my view, to judge React added complexity in this area, as 'deterioration'.

Ideally these types of things should have been solved by the compilers .. but javascript (and browser) ecosystem is probably 10-15 years away from even thinking about this.
Oof, it's going to be difficult to police this and prevent abuse.
That is only true if the outside contributes things that facebooks actually needs and if they are on a level of quality which facebooks wants. Often enough projects grow beyond the initial goal and at the end the maintainer is buried in meaningless work (for his own goals) and can't focus anymore on his own important things.
At 5 $ per month?
Whenever you post something negative towards China then your post usually end up at -2 ~ -5 before slowly climbing up again. I personally don't care about karma but I do care about text becoming less readable, so it's unfortunate that it's so easy to game the system.
@benji111
Not at all. I'm a casual user and I don't use scooters daily. I think anyone that uses a scooter daily prefers to buying one of his own.
Let's say I've taken one from my train station to my home in the evening, charge it, and then ride it back in the morning (creating more income for Bird) and leave it in the train station. It will be used all day long, and I don't expect it to be in the train station when I get back.

I think that just paying with bird credits reduce the entire "let's make a business out of charging" and will just create a better community.

As again, I think that this problem is completely solvable by Bird. And in other threads they've mentioned that there are many signals to those "hordaers". I think that Bird just don't want to deal with it since it has enough funding/focuses on market adoption.

It's the same with Microsoft and piracy tools of Windows. I'm sure they can crack it down completely, but it just don't bother them enough on the bottom line.
Rofi is pretty great.

I'm also shamelessly addicted to guake (drop down terminal). I know there are more robust alternatives, but having grown up with Quake/CS, it just feels right.
It can be completely optional. If someone is doing a great job as a charger for some time, they can be switched to being paid directly.
Looking at the design, it's clear that the team is trying really hard to make functions look and work like classes look. Variable declarations at the top, followed by helper methods, followed by lifecycle methods. Given that classes are themselves sugar to make prototypes palatable to a broad range of developers, it's certainly a tough design task; I'm not convinced that reliance on call-index is wrong per se, but it is magical (and magic in JavaScript is obnoxious).

That said, the presentation of the third and forth flaws seem a bit weak. useState accepts a key as the first parameter, but in both of the composite functions that input parameter disappears. That looks like a refactoring error.

From a design standpoint, if `useState(symbol)` is acceptable (and I'm not saying it is), then `useWindowWith(symbol)` would likewise be acceptable in that it's not adding any more requirements to the interface than the vanilla version.

Proper bookkeeping of symbols resolves the issues here. However, if the design objective is to reduce the effort on the developer to do their own bookkeeping, then call-order indexing does make sense.

(Not to mention that Symbols are not supported by IE11 which remains an important target for bigger companies.)

I'm not sure there's a good way out. When you look at solutions like Protocol Buffers, they just bite the bullet and require the developer to supply the indexing. If JavaScript had something like Go's iota, then you could imagine using an enumeration to supply the indexing without requiring everyone to type 1,2,3,4... etc. But it doesn't so, that's wishful thinking. Nevertheless, the react codebase itself does contain a giant list of assignments of Symbol() || number to constants, so it's a pattern you're already aware of.

A tough nut to crack.
Meng has been arrested for her alleged involvement in sanctions violations that took place sometime between 2010-2013 (i.e. during the U.N. Sanctions on Iran era), not for violations of the the current US-led sanctions.

https://www.bloomberg.com/news/articles/2018-12-07/huawei-s-...
Are you familiar with the phrase gatekeeping?
Frane Selak
Why the U.S.-China ‘Trade War’ Is Really About the Future of Innovation
In fiction, catching 50% - 75% of the payload on a long sentence is pretty good, especially for the first read-through. Mixed metaphors and wandering trains and all that.

In scientific and technical writing, catching 50% - 75% of the payload on a sentence is how human casualties happen.
People from all over the world are sending emails to Melbourne’s trees
Emacs org-mode[0]

From the website's description:

Org mode is for keeping notes, maintaining TODO lists, planning projects, and authoring documents with a fast and effective plain-text system.

I just copied some of the set-up from here[1]

[0] - https://orgmode.org/

[1] - http://doc.norang.ca/org-mode.html
Try our free BI tool https://www.seektable.com
It has PostgreSql connector; with 'flat table' report type you can easily filter/sort records without need to write SQL, and pivot tables/charts are good for summary reports (under the hood GROUP BY queries are generated)

BTW, SeekTable can connect to ElasticSearch so it may be used with this data source too.
Meng's arrest is for actions she allegedly took to help Iran evade sanctions years ago, during the period in which U.N. sanctions on Iran were in force.

https://www.bloomberg.com/news/articles/2018-12-07/huawei-s-...