HNHacker News
TopNewBestAskShowJobs

pbiggar

7,962 karma · joined January 26, 2009

Cofounder of Tech for Palestine (https://techforpalestine.org)

Previously founder/CTO of Dark (http://darklang.com), and founder/CEO of CircleCI (https://circleci.com). PhD in CS.

https://hachyderm.io/@paulbiggar

https://bsky.app/profile/paulbiggar.com

https://twitter.com/paulbiggar

https://blog.paulbiggar.com

Contact: paul@techforpalestine.org or paul.biggar@gmail.com

submissionscomments
pbiggar··on Thoughts on Rust vs. OCaml
Both are systems programming languages (OCaml describes itself as such).

The rewrite in Rust thing, for darklang at least, comes from the 50th time we've had to do something bad and ugly to fit into what is supported by OCaml.

pbiggar··on Thoughts on Rust vs. OCaml
Thanks! How does the Arena help you with pattern matching? I'd be very interested.
pbiggar··on Thoughts on Rust vs. OCaml
Yeah, it's really unfortunate. Dune and Esy are moving things forward, but you sorta have to know the ecosystem quite well to figure that out.
pbiggar··on CEO of Uber: Gig Workers Deserve Better
Thanks for the correction!

I actually confused my facts here - it's tipping I was thinking of that comes directly from slavery. Employer-paid health care just _continues_ because of racism, as opposed to being created by it.

pbiggar··on CEO of Uber: Gig Workers Deserve Better
Once you agree a safety net is a net positive, then it comes down to implementation.

In this case, the employer is the parent's employer. Which means that the people who can take the risk to create startups is limited to "people whose parents have health insurance". Which excludes a large section of society, including for example poor people.

(also--and this might be a bit of a jump for someone just learning about inequality of opportunity--but a fun thing to research online is "why is the US the only country with employer-based health insurance", especially once you discover the answer is "slavery")!

pbiggar··on CEO of Uber: Gig Workers Deserve Better
Startups are in the US because of a long chain of decisions and network effects that ultimately come from US military spending in the 60s.

> I quit my job and thanks to the insurance changes in the US a few years ago

So you're saying that you were able to take the chance to build a startup because of the safety net?

pbiggar··on Validating Kubernetes YAML for best practice and policies
I recently had a bug that wouldn't have happened if I'd had these in place: https://dev.to/darklang/a-fun-bug-55cl. I added similar checks (and kube-score and polaris seem like good tools - I might try adding them).
pbiggar··on Launch HN: Speedscale (YC S20) – Automatically create tests from actual traffic
This sounds great! We actually discussed doing this at the very start of CircleCI (we had a partnership with an exception handling service, but we never executed on it). Coincidentally, my current company, Dark (https://darklang.com) is based around a similar concept -- using live traffic as an assistant as you're writing code.
pbiggar··on Binary Search: A new implementation that is up to 25% faster
This is really cool!

About a decade ago I did research on sorting and searching, which was the same type of work going on here (https://github.com/pbiggar/sorting-branches-caching). I found it was extremely difficult to accurately say whether one algorithm is faster than another in the general case. I found a bunch of speed improvements that probably only apply in processors with very long pipelines (like the P4)).

Execution speed is probably the right metric here, but it makes it hard to understand _why_ it's faster.

PS. Looking at "boundless interpolated search" (https://github.com/scandum/binary_search/blob/master/binary-...), it seems it's missing a `++checks`. I initially thought this could be the cause of a misreporting it as being faster, but I see the benchmark is run-time based so that wouldn't cause it unless the incrementing itself is the bottleneck.

pbiggar··on Ask HN: How and when did you decide and start your startup?
I found it useful to have cofounders as forcing functions. Also, the end of the previous thing: college->first startup, finishing my PhD->YC startup, being fired->CircleCI, and running out of money->Dark.
pbiggar··on Whose Land – Indigenous Nations of North America
I took Westphalian to refer to the concept of the "nation state", which--at least in the west--is regarded to have been created at the Treaty of Westphalia.
pbiggar··on Darklang devlog #2: What next?
The main thing is that if Dark is it's own language, that we're freed of the legacy of whatever other language we might use, and can design something that's explicitly for our use case.

As an example, Dark has "live values" which is where at any point in your program, we show you the actual value for the expression you're on. We use "traces" for this, which means the input (usually a HTTP request) as well as saved results of every expressions.

To accomplish this, we need a language where we can mark which functions are pure, where we can instrument the runtime, and where we can play the runtime back in our editor, filling in the saved trace values.

So nothing wrong with python, but it doesn't have any of those properties.

Similarly, we want your program to deploy instantly. That means that we need a technical way to deploy in 50ms (not sure that's available in python), but we also need language features that support that (such as feature flags built in, and the ability to safely make changes to programs). Otherwise, you'd find it's super easy to break your program with a typo.

This stuff is plausible in Python and many other languages, but seems super difficult.

pbiggar··on Darklang Source Code Released
Thanks for posting! I’ll be writing a blog post this week to announce it officially!
pbiggar··on Dark Team Shrinks to One
No worries, and thanks!
pbiggar··on Dark Team Shrinks to One
Yes, we are extending the option exercise windows for 10 years. For folks who haven't hit their 1-yr cliffs, we waived the cliffs and so they vested for the time they were at Dark.
pbiggar··on Dark Team Shrinks to One
Thanks for posting (don't love the title though ;))

Startups are hard, and we were trying to grow something that hadn't gotten to product market fit yet. I'm working on getting to PMF, and thinking hard about what's needed to do that, while making sure Dark works in the long term.

pbiggar··on Why is Kubernetes getting so popular?
Just wanted to clarify that Dark isn't like Pulumi. The idea with Dark is that there is no configuration, just code.
pbiggar··on The naked truth about writing a programming language (2014)
Yeah, I think a bunch of people work like that. We've had the feedback that some people have had to change their workflow to work well with Dark.

People generally use what we call "trace-driven development", where they make a HTTP request to the code they're editing (typically, people are making APIs or backends to JS apps), and then they always have "live values" of what they're working on (similar to a REPL, or to running unit tests on a loop, but instantly).

pbiggar··on The naked truth about writing a programming language (2014)
The code always lives as AST, and the code that you see in the editor is a pretty-print of the AST. We don't go back and forth between AST and text - when you make a change in the editor, we look up the "token" where your cursor was, and use it to find the place in the AST that needs a change, and changes only that.
pbiggar··on The naked truth about writing a programming language (2014)
That's not really how Dark works. You're not manipulating text in your editor - you use our editor, and our editor only uses ASTs. So when cutting and pasting, you're cutting and pasting AST, not text. So to answer your question, you can paste an entire handler or function at once, but it will be one you copied from another place in DArk and it will be structured.

We've looked at allowing people to paste text (eg from Stackoverflow) into Dark. We think we can do it by just inserting each character one at a time (though there's a technical flaw with that at the moment, which could be addressed). In that sense, Dark is sort-of a parser (I don't know if it technically counts).

pbiggar··on The naked truth about writing a programming language (2014)
I had to look up whether you were technically accurate (I've a PhD in compilers but parsing's not really my thing), and I think the answer is "it depends, maybe?"

To get to the root of the issue though, there is not a parser.

Well, one could consider the function that takes each keystroke to be a parser - though I don't know if that's technically correct either. So perhaps the more accurate thing to say is there is not a step that takes a textual source file and parses it.

pbiggar··on The naked truth about writing a programming language (2014)
Think I made it more confusing, not less, sorry! Did you watch the video - it's clearer after watching it.
pbiggar··on The naked truth about writing a programming language (2014)
Sure. You can see it in action at http://darklang.com/launch/demo-video (also, we've gone through our waiting list, so we're pretty much adding new folks who sign up immediately, if you want to try it out).

The main idea is that you when you make a change (let's say, you type a key in the editor), that change happens directly on the AST (the internal set of objects that represent the program). So for example, if you're seeing:

    let x = 5
    x + 2

we represent that internally as `Let ("x", Int 5, BinOp ("+", Var "x", Int 2))`

In a normal programming environment, you type up text, and the parser converts it to the internal representation. With Dark, we always keep everything in the internal representation. That means, if it isn't a "syntactically" valid program, you can't create it in the first place.

In practice, this means that if you type, for example, `z` in the middle of `let`, in a traditional language you'd get an error like `lzet is not a valid token` and in Dark, the `z` just wouldn't appear (nothing would happen). So it's not possible to get a syntactically invalid program.

The overall idea with Dark is that programs are always live (and also safe). So to make that be true, we need to ensure that you don't spend a period of time in a state where we can't understand your program (such as when the syntax is invalid).

pbiggar··on The naked truth about writing a programming language (2014)
This advice is quite good for certain types of programming language, if you look at the world the same was as he does. We're implementing Dark from a completely different worldview, and from that vantage point, a lot of these aren't exactly wrong, but different.

> Syntax matters

The approach we took with Dark is that there isn't a syntax, per se, in that there isn't a parser. There's certainly a textual view of Dark and so it's important that the code looks good (it currently looks only OK, in my opinion). But as a result, we have other options for minimizing keystrokes (autocomplete built-in), parsing (again, no parse), and minimizing keywords (you're allowed have a variant with the same name as a keyword, which isn't allowed in languages with parsers (well, lexers, but same idea).

> context free grammars

No parser, no need to have a grammar. His point about IDEs is great - we only support our own IDE (a controversial decision to be sure!)

> Redundancy

This is an esoteric parsing problem, that only applies if you have a parser. No parser means no syntax errors. We are left with editor errors (how does the editor have good UX) and run-time errors.

> Implementation

He's right about how hard error messages are, so I feel good about our "not parsing" approach.

> Compiler speed

Our compilation is instant. The way it's instant is:

- very small compilation units: you're editing a single function at a time, and so nothing else needs to be parsed.

- no parser: The editor directly updates the AST, so you don't have to read the whole file (there isn't a "file" concept). Even in JS, that means an update takes a few milliseconds at the most.

- extremely incremental compilation: making a change in the editor only changes the exact AST construct that's changing.

> Lowering

This is really about compilation. One thing you can do, which is what we do, is have an interpreter. Now, interpreters are slow, but we simply have a different goal with the language, which is to run HTTP requests quickly. We do run into problems with the limit of the interpreter, but we plan to add a compiler later to deal with this.

Really what I'm suggesting here is that compiled languages look at having interpreters in addition to compilers.

> i/o performance

> memory allocation

I think he's approaching this with an implicit goal of "it must be as fast as possible", which isn't necessarily a goal for all languages.

> You’ve done it, you’ve got a great prototype of the new language. Now what? Next comes the hardest part. This is where most new languages fail. You’ll be doing what every nascent rock band does — play shopping malls, high school dances, dive bars, etc., slowly building up an audience. For languages, this means preparing presentations, articles, tutorials, and books on the language. Then, going to programmer meetings, conferences, companies, anywhere they’ll have you, and show it off. You’ll get used to public speaking, and even find you enjoy it (I enjoy it a lot).

Well this is certainly correct!

pbiggar··on Ask HN: Is HN a ‘healthy online community’? I’m doing a case study for a class
In a certain sense, everyone in tech is a HN member. It's a community that's much bigger than just the people who post here.
pbiggar··on Ask HN: Is HN a ‘healthy online community’? I’m doing a case study for a class
Look on twitter what people think about HN. The general opinion I hear about "the orange site" is that it's a toxic trash fire (this is also my opinion, which I will not be defending here).
pbiggar··on Containers Are Not the Future
I wrote a satirical blog post on Docker/k8s in 2015 [1]. At the time, I actually felt docker was the future, but it became clear over the next few years that it was too much. The complexity of docker /infra/devops is overwhelming, and something much much simpler is clearly needed.

I don't know if Dark (my startup trying to solve this) is going to take over, but it's pretty clear that the current complexity is unsustainable.

This goes double if recession/layoffs/etc is happening due to COVID. People are going to need to spend a lot less on engineering, and the amount being spent on engineers that maintain infra is an obvious starting point. I would expect people to switch to much simpler infrastructures, and reduce the complexities of their stacks by necessity.

[1] https://circleci.com/blog/its-the-future/

pbiggar··on Across furtive videocons, junior VCs wait for the layoffs to begin
> Third, and this is rarer, some funds have made loans or real estate investments using their management fee income as a way to boost the salary returns of the general partners.

They what?!?

pbiggar··on New MacBook Air released, pricing now starts at $999, features Magic Keyboard
Imagine for a second that you were constantly being assumed to be an incorrect gender. And let's further assume that it bothered you. Would you want to spend all your time telling people to not assume your gender (and consider the high possibility that they're going to get a reaction like this)?

No, you're not. And so every dude on this thing is going to use "he" everywhere cause "no-one's complaining". And then when people who prefer different gender pronouns come in, they're going to see people being assholes about gender pronouns, and they're going to say "fuck this" and leave (note, they're not going to reply either, cause they also are sick of it).

And so to prevent that, people other than the "supposedly offended person" need to step in, even if they weren't asked.

I'm not going to reply to further discussion here. I hope this was useful to you.

pbiggar··on New MacBook Air released, pricing now starts at $999, features Magic Keyboard
> Did anybody ask for an opinion on that?

Don't be an asshole.

Parent misattributed the pronoun, sure. And then they were asked to not do that.

← PreviousPage 15 of 34Next →