News for hackers. Stuff that matters.

cbreeden

Re:About This Googler's Manifesto on Sunday August 06, 2017 @11:30AM (#14941682)
Lol, your comment makes it seem like it wasn't a hyperbole.
Re:LaTeX Math in MS Office on Sunday July 30, 2017 @08:52PM (#14888794)
Don't tell them that Microsoft developed the OpenType Math specification that LuaTeX uses.
This is weird. I'm extremely surprised that some kind of statue of limitations does not apply here. I'm not sure we are getting the whole story.
Re:2017 Rust Roadmap on Saturday October 22, 2016 @11:28AM (#12769050)
No sure why you were down-voted, but it probably has something to do with connotation. I agree though -- library maturity, tooling maturity are also very important factors when it comes to productivity. A steep learning curve, however, probably has less to do with productivity and more to do with adoption, which I think is what the parent was trying to get across.

But, of course, adoption rate can indirectly impact library and tooling maturity. :)

I don't understand. Ref: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634757. This project was put up for adoption, and many people replied showing interest (even some creating PPA's) but ownership was never transferred and it is still listed for adoption.
Re:Multiple Bugs in OpenBSD Kernel on Thursday July 14, 2016 @09:04PM (#12098364)
Ya I was quite impressed.
I don't understand the shopping results argument listed on the top of the pages for search results. I have personally never confused them with actual results, and doesn DuckDuckGo Bing and Yahoo do this? If so, then why single out Google?
Re:Ruma, a Matrix homeserver written in Rust on Tuesday July 05, 2016 @10:18AM (#12036570)
Indeed you beat me to the punch. You can totally use unsafe. This just means that the compiler essential is unable to _prove_ that your code is memory safe. That does mean the author can't. Documenting unsafe points in your code gives also tells you where to look if you do start seeing memory related problems, which can be helpful for debugging.
It's still not clear to me. Are you suggesting that uses not be notified of a potential yet not verified security hole or not?
Maybe it's more like: hey, I see that you bought that phone at Walmart. You better give Walmart a 30% cut from that phone bill!
Re:Visual Studio Code 1.2 released on Tuesday June 07, 2016 @03:40PM (#11857170)
F1 then type trim. The first option to pop up should be the trim whitespace command. Hit enter. Or there is an option to trim automatically on save.
Re:Flow vs. Typescript on Monday June 06, 2016 @03:54PM (#11849790)
Python added type hints in version 3.5. It's a good checklist for dynamically typed languages with optional static typing I'd say.