mustpax

I feel like I’m missing something. How do people justify the security implications of manual memory management when building a publicly accessible web service with Zig?

Once I create a presentation, can I hot-link to a png of it as a cover image? I don't know if I need the full richness of a ppt/pdf off the gate but image gen with solid text layout would be huge.

Someone should write a blog post about the prestige/effectiveness negative feedback loop. This is also the Achilles heel of top tier SV VCs including YC.

Really well put. “Processes is a symptom of competence, not the cause” is a good motto.

It’s always a good sign when an architecture diagram has Nginx + Lua in it. The Lua memory leak bug is a good example of why it saves SO MUCH time to use managed services like Browserless to do things at scale. When you DIY, you end up debugging a ton of these little things when there is much higher ROI code you could be writing.

In that case Windows Linux Subsystem seems like a good compromise.

Alfred's clipboard manager will auto-exclude anything that's copied from 1Password. You can add more auto-exclude rules yourself too.

Horizons School of Technology | Architect in Residence | San Francisco, CA | Onsite Full-time or Contract | $120k-180k http://www.joinhorizons.com/

We are looking for a Architect in Residence who is a seasoned software engineer with 5+ years of experience and deep technical and professional insights.

As an Architect in Residence you will spend 3-9 months at Horizons. During this time you will mentor students one-on-one, teach advanced subjects in a classroom and oversee ambitious student projects.

We are a group of entrepreneurs and former engineers in technology who are passionate about bridging the gap between traditional education and the tech world.

Our students have gone on to win national hackathons, land jobs at tech giants, and raise money for their startups. We find high-potential, ambitious undergraduates from (many from top schools) and we fast-track their careers by empowering them with technical skills and a professional network. Our 12-16 week immersive program teaches full-stack web application development, entrepreneurship and software engineering.

To apply email your resume to [email protected]

Job description: https://angel.co/horizonsbootcamp/jobs/187808-architect-in-r...

The reason that this is on the front page is because not everyone is a serious astrophotographer.

If you find yourself asking "I already know about this, why is this on the front page?" Take a moment, you've just answered your own question.

You hit the nail in the head. Intel has built up amazing margins on the x86 business over the years by beating out competitors. ARM margins are razor thin by comparison and Intel can't bring themselves to cannibalize their cash cow by becoming another ARM manufacturer.

Thanks for the explanation. Congrats on the fundraise!

Out of curiosity, do these major donors receive partial control over Watsi in return? If so, what's the mechanism for that? Board seats?

Anyone have reading suggestions for an operationally minded infrastructure engineer who is paranoid about security and hates breaking production but still wants to take the IPv6 plunge?

Lack of generics is part of the reason why Go is easier to learn and the Go compiler is faster than, say, Rust.

Sure, generics don't have runtime overhead in Rust and Haskell but they have other costs. You always pay for abstractions some way.

There's no question that Rust and Haskell have better tools than C++ for abstracting code. Go is just demonstrating that you can write great software without the aid (and cost) of generics.

Exactly! Go makes the cost of generic code explicitly visible.

Generics encourage over-generalizing behavior that runs counter to writing highly performant code. If you care about speed, you don't spend time making your code generic. You optimize closely to your use case.

That's true. It's not just GC actually. Slices and goroutines don't have a direct analogues in C either. But it is fairly easy to reason about the runtime complexity of these conveniences.

But like I said, if I didn't care about GC or concurrency, I'd be writing C.

By systems programming I mean writing the code that applications and distributed systems run on top of. Raft (https://github.com/goraft/raft) and groupcache (https://github.com/golang/groupcache) come to mind as examples.

That's a good point though. A lot of people mean different things by systems programming.

There's something very seductive about languages like Rust or Scala or Haskell or even C++. These languages whisper in our ears "you are brilliant and here's a blank canvas where you can design the most perfect abstraction the world has ever seen."

But, for systems programming, abstractions suck. They always, always have a cost. When abstractions break, you not only have to deal with a broken system but the broken abstraction itself too. (Anyone who has ever seen a gcc compiler error for C++ knows how this feels.)

Therein lies Go's value proposition. It does not make it possible to make things pretty (ugh, nil). It just makes it impossible (ok, really hard) to overcomplicate things. When you write Go code, you can picture what the C equivalent would look like. You want to deal with errors? Here's an if statement. Data structures? Here's a struct. Generics? Here's another if statement, put it inside your for loop.

Obviously, Go is not the right choice of language for most things. When you're doing application development, you may be able to afford the cost of abstractions. But for tools that only need to do one thing and do it extremely well, it's either that or C. And I'm not going back to managing my own memory anytime soon.

Since I am not flying the plane, how could I possibly cause you to "lose your ass in an accident" because my attention is on Angry Birds? The emergency maneuvers performed by airline passengers require prompt obedience but not lightning reflexes. There'll be plenty of time to put down the Angry Birds.

For the 44 to 24 percent of students who passed the course, this was not a failure at all. I don't see why they should be denied access to education because the likelihood of failing the course is higher. Online courses should be offered cheaper than regular on-site courses to take the increased risk into account, but that doesn't mean they should not be offered at all.

Many price points, many products.