skysight-inc/HackerNews huggingface dataset:
I couldn't agree more. I like how he is very pointed at C/C++ and doesn't mention any of the safer, garbage collected languages....OH NOES, they have issues too!

Java: https://www.exploit-db.com/exploits/36101/

.NET: https://www.exploit-db.com/exploits/35280/

Python: https://www.exploit-db.com/exploits/33251/

At least my code/data running in "the cloud" is safe:

http://www.jcomputers.us/vol9/jcp0904-30.pdf

https://www.cs.unc.edu/~reiter/papers/2012/CCS.pdf

I can keep going here but you get the point. Perhaps he should have also taken it further and proposed that we move onto Mill processors since the underlying hardware has a history of issues:

sinkhole: https://www.exploit-db.com/exploits/37724/

rowhammer: https://www.exploit-db.com/exploits/36310/

Yes in C/C++ you can make mistakes (#gotofail) but in other languages, I would argue you can fuck-up in ways that are not nearly as obvious such that static analysis can't catch. A nicety about C/C++ is the tooling has gotten pretty damn good over the last 43 years (clang, gcc, valgrind, etc) and can catch most of these kind of bugs. The onus is on the developer to do the correct thing though and it appears that over at Adobe, etc that they (historically) could give 0 shits about doing this. It honestly seems to be though, that they are tightening up things.

Perhaps we should rebuild everything from the ground up....
The Airy ellipsoid is still used by the Ordnance Survey in Great Britain. (Northern Ireland has a different national grid based on a different geodetic system.) WGS84 may be increasingly “the standard”, but it isn't the only geodetic system in widespread use. ETRS89 is anchored to the European continental plate, and is therefore slowly drifting out of sync with WGS84.
I don't understand this type of reaction every time the problems of C/C++ are highlighted. Yes, of course the problems can be migitated using tools, but clearly this is not being done or is not as thorough or practical a solution as making it the language's responsibility. There's hoops that you must jump through to make C/C++ safe and clearly this just doesn't happen in practice. The same hoops just don't exist for Go and Rust (and that's just the system(ish) programming languages) and therefore I disagree that you can handwave this away as bullshit.
With a bare bones designe, if you are unlucky, your arm/leg won't get stuck, but get crushed or detached (violently)

Step out a tad too late while going down and trip on the unexpected step up you have to make, and a few seconds later, the top of the box may break your ankle. The falling _will_ happen, in particular to elderly with weaker bones, so you will have to come up with a solution that stops the device _fast_ if that happens. At the same time, for reliability, the device shouldn't come to a stop if someone heavy steps or jumps into a box.
discussion: https://news.ycombinator.com/item?id=10053561
The GIF makes it look like the planets are trailing behind the Sun, which they are not at all. They orbit, so they constantly pass in front of it as well as behind it relative to its movement in the galaxy.
Swift's Error Handling
Doesn't work on Xfce either. On a virtual terminal thingy (ctrl-alt-f1) it shows a grey background with white text. I suspect blink is only implemented on the Mac's terminal, not in Linux-land.
I try not to let positive feed go to my head by focussing on people better than me and knowing how much room there is for improvement. I try to take negative feedback as a gift pointing to the right improvements to aim for.
To a degree this ammuses me greatly. Rust allows you to opt-out of safety. While your proposal (which I agree with to be clear) allows you to opt-in to safety in C/C++.

This really cuts to the core of ideological differences between C/C++ and Rust camps. C/C++ programmers tell the compiler trust me, while Rust programmers say check me. I can't help but feel to a degree the Rust ideology is superior. To make by bias clear I work in C, and write in Rust in my spare time.
You were more concerned with whether or not you could you never stopped to think whether or not you should
Island Ludi
On Post-Democracy
>But we also have to acknowledge that we as a profession are not able to write secure code in C/C++.

You can't write safe code in any Turing complete language. That's the whole point of Turing completeness. The only reason why memory attacks are as common as they are is because C like languages are the most popular ones.

If we replaced everything written with C to a "safe" language like, I don't know Haskell?, we'd have just as many zero day exploits of the monads within programs.
I've never actually used Rust myself - I'm just familiar with their goals: so I'm not entirely sure what you are referring to.

Just keep in mind that the amount of work done on the various C++ compilers is most likely measured in man-decades, where Rust is probably still man-hours.

Do you mean a directed graph or a graphical graph? I've implemented directed graphs in at least two different managed languages (which are more constrained than Rust) and had to use no unsafe breakouts. There might be some complexity for some reason with Rust, but if it's possible in a managed language then surely...
iTerm2 has an option in your Profile: Text tab > Text Rendering: "Blinking Text Allowed"

Off by default; enable and blink like its 1989.
> It is not even clear how a safe language that would permit this would look like.

If this hypothetical browser is implemented in a safe language that runs on a JIT-compiled environment itself, then it could compile JS to that same safe language and allow that same runtime environment to JIT-compile the resulting compiled JS.

Would that make sense? (I have no empirical data to back this up, but i'd like to know if at least hypothetically this approach could work)
Why? Go seems like a reasonable choice here: it's much, much safer by default than C and much, much simpler than C++. I mean memory safety, mostly. To me it seems that Go is actually much better suited for things like these than for webapps that some people use it to write.
No, Ottawa.

A quick search shows that some lighter duty winches will draw 60-90A, while heavier duty winches can easily draw ~250A to ~350A.

The winch I'll be installing next month as a 10,000lb pull rating. That requires a lot of power.... (Why 5T? Because my Jeep weighs a hair over 2.25T, and if it's stuck in the mud, I'll need to overcome the mud....)

A winch is typically connected directly to the battery and is controlled via a relay: The control cable uses very low current to activate/deactivate a solenoid that switches the winch on/off.

(It's an interesting and ironic bit of jargon: When winch owners refer to a winch's solenoids, they are referring to the control relays... ...but any winch contains at least three solenoids, one low-draw solenoid in the relay, and two high-draw solenoids in the winch itself, that is, the electromagnets that are the heart of the motor....)
garbage collection makes not a language safe
There are no secure systems written in ANY language (to my knowledge).

At the end of the day all computers and systems can be broken. Using C/C++ might open up that up to being more likely when someone isn't thoughtful enough in the implementation. The trade off comes in when you want to risk the higher chance of security problems for the better performance.

This is just my opinion, I believe that we spend way too much time writing in these 'safe' languages at the cost of performance when it often isn't really needed and in the long run just adds to the bloat of our systems. This comes from my belief that if anyone is willing to spend the time and money to break a system they will. So why are we burdening our piggy banks with the same security as our bank vaults?
Honeycast – View, setup and record honeypot sessions
> So what language to you propose we use to rewrite all video and audio software? Javascript, Lua, Brainfuck, what?

It's not proposing a particular language; only a property was proposed: memory-safety. This was defined loosely:

> Garbage collection was invented in 1959, for Lisp, the first memory-safe language. It provides the foundation for memory safety and it is used in most memory-safe programming languages today. (It is also possible to have memory-safe languages without garbage collection, e.g., Cyclone or Rust.)

We could compare this with other properties of programming languages which have been tried in the past, but are now considered bad ideas or a last resort:

- DWIM (Do What I Mean): if a name (function, variable, etc.) doesn't exist, use one with a similar spelling

- Ignore errors by default: eg. Bash without "set -e", visual basic's "On Error Resume Next", etc.

- GOTO: still useful on occasion, but no longer the "go to" control structure in most code (pun intended)

- Dynamic scope by default

- NULL: Perhaps controversial, but also infamous. Can be tamed with nullable types, or eliminated with option types.

- "Loose typing", ie. the casting rules in PHP, JS, etc. which break symmetry and transitivity of "=="

- Automatic semicolon insertion: Either require semicolons or don't; trying to guess leads to problems

- Name-based typing: eg. in FORTRAN any variable name beginning with I, J, K, L, M or N are implicitly ints, anything else is implicitly float

I would certainly consider memory unsafe languages in the same category. There's no need, now that we have garbage collection and linear types.
I feel you may not have given much charity to my initial statement, but that's the internet so whatever.

It's economies of scale when it comes to cameras. RED family is most certainly on the higher end of cameras when it comes to all brackets of film production. Maybe Alexa is weapon of choice for most DPs, but some prefer the more buttery and filmic motion you get with an Epic Dragon (not me, I prefer the neutrality of the Alexa).

I'm betting my lunch that Ursa Mini (with a brand new, BM, custom built sensor) will do what the 5D did in 2008 for the indies. Test an Ursa original (old, factory 4k sensor) against a Dragon with the same glass and it's difficult for most to call out which is which. Given this will be a bigger and better sensor ... well south under 5k ... with all the fixed noise patterns rectified, I think it really could allow indies to flex.
If you're interested in the historical setting of Longitude (and why it's in Greenwich to begin with), I highly recommend Dava Sobel's _Longitude_: http://www.amazon.com/Longitude-Genius-Greatest-Scientific-P...
DMCA Complaint from Columbia Pictures for videos with “pixels” in title
Immature to one is playful to another. :-)

It's all going to depend on the team; it would be a mistake to conflate seriousness with competence.
Microsoft could be found to be sacrificing babies and it wouldn't make a jot of difference to their bottom line.
Except when it isn't

http://www.saintcorporation.com/cgi-bin/demo_tut.pl?tutorial...

http://www.cvedetails.com/vulnerability-list/vendor_id-97/pr...
I only cared about C in 1993 and am into computers since 1986.

Only developers with access to expensive UNIX workstations cared about learning C.

Yes, the widespread of UNIX and C as its language is one of the reasons the CVE database gets updated every day.
I wouldn't think so: (1) refers to rules for changing rules, including amending rules, and (2) refers to rules for changing amendments to rules.

Logically, both rules and amendments to rules must be mutable in order for these rules to be required. If a rule or amendment were immutable, one would no longer require rules specifying how to amend them.
What buffer overflow? Obviously the firmware is formally proven correct and proven not to include any of those?

(I'm half joking here - I suspect that's not the case and won't be the case for a foreseeable future, but I'd be happy to learn I'm wrong here)
> If we replaced everything written with C to a "safe" language like, I don't know Haskell?, we'd have just as many zero day exploits of the monads within programs.

I disagree. There will always be security issues, due to (ab)uses that developers didn't consider, but there can be different probabilities. Requiring developers to learn about language gotchas, remember those gotchas when coding, and jump through hoops to avoid them, just stacks the odds against us.
I never said anything about living off the grid having a requirement that you had to build everything yourself in the process of leading up to you living off the grid.

How you get to the point in time where you start living off the grid is irrelevant when the question is, am I living off the grid.

Q.) Is paying someone to come dig a well really that different than buying water?

Yes. One leaves you being self sufficient. One doesn't.

Q.) What if he was hypothetically able to purchase and store the amount of water that would be required to live the rest of his life?

Then he would be self sufficient and living off the grid.

Q.) What happens when the well dries up?

He finds another source of water, or dies. Perhaps he would have to rejoin civilisation to prevent death.

Q.) He gets someone that is on the grid to drill a new one? Doesn't that put him by proxy back on the grid?

If he does it that way. Then yes. Temporarily.
Software Engineer at Telenor Digital AS - Trondheim, Norway

Permanent position, Full-time You can apply at - http://tinyurl.com/nc9okjm

We offer a position that will make you part of a hard core software development house. You will join a team of world class developers that feel strongly about what they are making.

About the job
We are a growing bunch of software engineers, working on an ever-changing list of exciting projects. Working in Telenor Digital gives us the tremendous opportunity to reach millions of users, across borders, cultures and languages, with our code, with the flexibility to choose the technology that does the job best. Exciting challenges at huge scale and high speed!

If this is you or who you want to be, we want to hear from you:

We want coders that are challenged by complex problems in distributed environments, but value simplicity in their solutions. We want software designers that look at the entire system and think like engineers - you look for data to validate your assumptions, you create tests to verify your implementations, you know your tools, and you look for opportunities to automate everything. You want to learn how all the parts work together - you want to know what it takes to run your code in a global production environment as much as you care about writing and debugging it.

You have a M.Sc in Computer Science or equivalent experience, and have worked with various programming languages, like Java, Go, Scala, C++ or Python. You are excited by distributed systems, cloud computing, and service-oriented architectures. You keep your code in a version control system, possibly distributed like git or mercurial, and you use more than your brain to keep track of your ideas and bugs. We don’t care if you’ve used the technologies we’re currently working with before. We DO care that you think they’re cool and something you want to work with.

We want smart people who will fight for their point of view because we’re often wrong, we just don’t like admitting it. We want co-workers who want to constantly learn new things and are capable of fluidly moving between projects. We want teammates who can quickly become subject matter experts in new areas and share that knowledge with the team and with the company. We want colleagues who take pride in what they do and want to share it with the world. We want engineers who are excited by contributing to open source projects, writing blog posts and speaking at conferences. We want people who want to dive into projects supporting Telenor’s business units all over the world.

The position is located in Trondheim.
We conduct background checks on relevant candidates.
Many older games now run good to perfect on wine.
love RED. We shoot aerials with RED Dragon - http://londonhelicam.co.uk

The footage is like butter in terms of dynamic range. Just wish they made more of an effort in terms of making it more affordable.

Blackmagic is another great innovative camera company, based in Australia. Both them and RED have a very involved, hands on founder with a clear vision of what cameras should be like and pushes for the future now - something that gives them an edge over the Japanese camera corporations.
Well, with this line of reasoning I do live completely off the grid already. I could build a water turbine or even a hand crank, but buying power from utilities is cheaper. I could start a farm, but going to grocery store every other day is cheaper as well. I could move far from civilization, but living in a 1M city is much more fun.
It does work in urxvt and konsole (and there's an option to turn it off). And as tempodox said, this is just VT100 stuff.
Rust is the right approach since it figures everything out at compile time. But it still has to prove itself. And what is the timeline for a browser completely re-implemented in Rust? 5 years? 10 years? Suggesting that throwing away and rewriting our entire software foundation that has been written in the past 50 years is just silly. To be realistically achievable we need an incremental approach to gradually analyze and fix old software instead of throw-away-and-rewrite.
I'd assume you'd have to call the 800 number
Not if you try something like PlayOnLinux. I've managed to run quite a few golden oldies that way.
Is this project still maintained? I don't see any commits since 2013. I saw a demo of this when I used to work at TW and gave it a shot and it worked like a charm. Unfortunately, I couldn't find any rspec3 runners!
This

https://www.blackmagicdesign.com/gb/products/cinemacameras/t...
Nice tool .. not able to run it though. (No Windows here.)

In the meantime, found this interesting related article, which inspires a bit of hacking as its a tad more technical and a little less .EXE'ish:

http://www.codeproject.com/Articles/6960/Steganography-VIII-...
It's not exactly what you described, but you may like reddit.com/r/battlestations
For what it's worth (and I intentionally didn't point this out in the parent), you can make a safe graph library in Rust with a typed arena (slightly less ergonomic and faster) or a refcounted smart pointer (slightly more ergonomic and slower). But this still does not validate your point, since the memory allocator is in many cases unsafe.

On how to ensure correctness of the `unsafe` code: that was what we were doing with the entire C/C++ code for decades, so what's the problem? We could however concentrate on the much less amount of code if we were using safer languages.
This seems really awesome.

I'm using CircleCI, they have an experimental option to collect junit xml files and give you a nicer output as well as try to make parallelization smarter, but the smart parallelization feature only works when you're using the inferred test command :(.

One really nice feature that caught my eye: "In addition to balancing, TLB does other interesting things like re-order tests within a subset(set of tests that run on a partition) before they are executed. For instance, it re-arranges tests to execute failing ones(that failed in previous build) first, hence ensuring early feedback."

I haven't read through the docs in detail, so maybe this is a stupid question, but wouldn't it be better to have a single service that includes the data and balancer and exposes functionality through a REST API? Then you could use it with any language, without having to install java on the machines that are running your test.
I hope it gets funded!
To be clear, I love Rust's approach to safety. I just don't think it is an realistic expectation that we can re-implement all security-critical C code in Rust until the sun goes super-nova ;)
This is not a critique of MVC, but rather the particular implementation that Backbone provides. With React you still have your models (and controllers).

And adding a new option may make an existing one obsolete. Remember ES3? I do, but I wouldn't want to write new code in it. Once new options were added (ES5, and then ES6), they made the old one obsolete. It desn't mean you can't use the old options, but why would you if the new ones are superior?
It's not "for free" it is free. No quotes.

Every dollar taken out of their pocket to pay someone else's bills is less money they have to spend on their children's education and for taking time to travel, among other things.

Generosity is a private choice and government has no business in making it public, except that it buys votes to empower politicians.
>Precise?? You're joking right? Given that the number of bits necessary to encode a message is highly depending on the way your message is interpreted..

The interpretation is not the language. If a message consists of words, or is mapped thereof; then there is an exact number of bits necessary.

>If your bits are interpreted as either black or white, I need only 1 bit to send a message indicating a color, if your bits are ASCII strings I need more bits to send the same information..

It seems like you are not familiar with the definition of bits. It is the binary measure implicit to boolean algebra. Bits are not specifically ASCII strings, because the former is a subset of the latter's characters.
What3words
You may like wayswework.io.
Should Your Startup Go Freemium?
Memory-safety doesn't make a language slower. Garbage collection does, but there are other approaches like linear types which perform all checks at compile-time, so the resulting code doesn't need to do any checking/indirection/etc. and is hence equivalent to what C would produce.
Oh yeah, Stamford.

Where $900/mo got you a 1BR apartment over someone's garage 20 years ago. Wonder what it gets you now? I forgot how bad Fairfield County was after I left.
I find it a bit unintuitive that "no change" errors are valued the same as "opposite" errors (e.g. answering "positive" when the change was actually negative). I find it far less interesting when the discrepancy is whether there is any change or not than when the effect is actually opposite to what one would apparently expect.

Additionally as others have pointed out some of the questions and answers aren't very clear (though maybe it's just my reading comprehension that's failing). I too am unhappy about the way the elderly question is posed -- it's not clear whether all of the programs were actually focussing on reducing mortality. In fact the introduction mentions that it's merely one of several goals and from anecdotal evidence I would expect that the mortality metric is thrown off by patients stabilizing once their health has deteriorated enough to require them to be placed under permanent care -- that you're less (or equally likely) to die doesn't mean you're more (or equally) healthy.
Git is no good for binaries. And SparkleShare is dead. The proper alternative is SyncThing https://syncthing.net/ I have it on my home and work laptops, a NAS and a VPS and it just works brilliantly.
Using movies & books as support for learning a language works quite well. Choose stories & topics that interest you and it helps you keep going even if you don't understand it all (yet).

I never needed an app for that but if the app supports you well in finding material, it might be worth it.
The ultimate infinite laws of probability test – Twitch plays Dark Souls
While the content is great, the tech seems bloody awful. Why is it so slow to load? It takes 5-10 seconds to load on both my laptop and my desktop (both < 1 year old) and I have nice fast fibre. Why would you start with a loading screen in this day and age? And worse a loading screen that doesn't tell you what it's loading. Flash is dead.

It severely impacts the usability, it looks like nothing is happening and I can imagine a lot of people just close it before it loads.

And it's (virtually) static content! Why doesn't it load with the opening page at least?
Humans definitely killed off woolly mammoths, giant armadillo
Mill processors? Aren't they still in research stage, only using emulation and no hardware.