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 Structural OCaml Editing in Emacs
Yeah, I was mostly influenced by paredit, though I had looked at parinfer and a few others.

Question about your approach: what happens if the code is syntactically invalid? Dark prevents code from being syntactically invalid cause it's AST only, but for example ocamlformat just refuses to run if it can't parse the whole file.

pbiggar··on Structural OCaml Editing in Emacs
Very cool.

We built a structural editor for an OCaml-like language (Darklang). Our first version was very AST-based, with all movement using the AST. The feedback we got was that AST-based editing is hard to grok and that you need line-based editing too. So we re-implemented and now we have both (although we broke and are re-adding a bunch of the editor refactorings).

pbiggar··on HOPL IV: History of Programming Languages – Accepted Papers
I was super lucky to be able to go to HOPL 3 in 2007. Amazing conference. These papers are a little less exciting to me, but it sounds awesome all the same.
pbiggar··on Facebook tax court trial begins over Ireland offshore deal
> "Facebook Ireland and Facebook’s other foreign affiliates - not Facebook US - led the high-risk, and ultimately successful, international effort to sell Facebook ads,” the company said in a pre-trial memorandum.

This is hilarious! Does anyone really believe the pretense that these are multiple different companies?

pbiggar··on GitHub: Increased Error Rates
Ah yes, on-prem software: where instead of having an outage and someone has to go fix it, you have an outage and _you_ have to go fix it.
pbiggar··on Coders at Work on finding and preventing bugs (2015)
All error handling is fundamentally the same. I think this one is as far from exception handling as possible while still being error handling.
pbiggar··on Coders at Work on finding and preventing bugs (2015)
I have a pattern that's working really well for us in the codebase, which I call `recover`.

Anywhere where you're tempted to crash because it's not possible, I add

    recover debug_string debug_values return_value
Recover prints a stack trace, notifies Rollbar, and then continues with the return value. As a result, we see whatever is going wrong with the code, but the program doesn't crash on users. And since we're using OCaml (strongly typed), we end up having decent guarantees of safety.

Works pretty well for us.

pbiggar··on Pentagon Requests $15B for Space Force
Sounds like they've identified $15B in wasteful spending that they can just eliminate.
pbiggar··on Anders Hejlsberg on Modern Compiler Construction (2016) [video]
It's not suitable for all purposes, but it's suitable for all editor purposes (including an in-editor execution engine). We don't do GVN, or any optimizations really, right now - I'm sure when we have a compiler of sorts we'll have other structures, SSA, etc.
pbiggar··on Anders Hejlsberg on Modern Compiler Construction (2016) [video]
This is kinda how the compiler-stuff in Dark is written.

Everything - the editor, semantic analysis, version control, execution engine, everything - all use the same data structures (the same abstract syntax tree).

We use functional data structure everywhere and we do functional updates within the AST all the time; that's even how text entry in the editor updates the program.

pbiggar··on Monoliths Are the Future
We have a similar thesis in Dark. People do microservices because they have to (well, some people have to, some people do them cause they're shiny). But in terms of actually understanding your application, microservices really don't help. And they bring so much complexity with them.

Our concept is to allow the decoupling of microservices, with the tooling of a monolith. Kinda hard to describe and we haven't done it yet, but basically give you the ability to write it as a monolith, but also have the separate scalability/deployment of a microservice.

pbiggar··on PopSockets CEO calls out Amazon's tactics before House committee
If congress wants to investigate Amazon's anti-trust stuff, they should spend some time looking at AWS.
pbiggar··on VCs Are Just Tired
This is a great article, especially because the solution is right there in the text:

> forcing everyone to chase the same set of SaaS companies

> everyone can read the gridiron of SaaS metrics

There was a perfect storm: huge seed rounds leading traditional firms to move upmarket, VCs raising larger funds and so needing to hit the winners hard, which caused Series A metrics to swell, and so VCs are all chasing the same deals.

Of course those deals don't need them: those companies are already winning and don't need their expertise, just their money, which is commoditized by the swelling of funds.

The answer is simple: chase less successful. Stop just trying to get into the big SaaS deals, and target smaller companies, lower metrics, earlier stage companies.

Of course, if the firm staffed up and raised a larger fund as the article says, then it may be structurally impossible to survive. Innovator's dilemma in action.

pbiggar··on Compiling Dark to SQL
Author here: let me know if you've any questions!
pbiggar··on Rete: JavaScript framework for visual programming and creating node editor
No, it's pretty current. The "code" in Dark is textual (it's not bytes on disk, but it's very far from nodes and edges). Dark is intended to be very code-y - although we're not fully there just yet coding in Dark mostly much feels like coding (discounting having to use a different editor).
pbiggar··on Rete: JavaScript framework for visual programming and creating node editor
We started with trying to create something like this when we started Dark (https://darklang.com). We ultimately moved away from this style of programming, as we couldn't figure out a way to make it feel "code-y" enough for people to want to write programs in it.

I'm super interested in what folks want to use this for?

pbiggar··on Is Git Irreplaceable? (2019)
To be clear, it's two concepts, one for branches and one for comments.

The first concept we've been calling deployless, and discussed it here: https://medium.com/darklang/how-dark-deploys-code-in-50ms-77...

The second one is just an idea right now, suggestions welcome. The observation is that comments on a particular line of code are spread in as many as a dozen places (a google doc, slack, trello, the code itself, an old version of the same code, PRs on github, comments on commits on github, commit messages, another place in the codebase referencing this one, the docs folder in your repo, another repo that uses this API, your 3rdparty docs on README.io, etc). This is weird and bad, and it must be possible to do better.

pbiggar··on Is Git Irreplaceable? (2019)
I'm working on a git replacement, in a way. The thing that makes git powerful is that its just text. Git is probably the most powerful thing for code as text. When code no longer is just text (and by "text" I mean bytes on disk, not that we're switching to coding with emoji or VR) you get to do more powerful stuff.

Our plan in Dark (https://darklang.com) is to combine all the different ways that people "branch" (deployment, feature flags, git branches, staging/dev/prod environments) into a single concept. And then we also plan to combine all the ways to "comment" (PRs, slack messages, commit message, code comments) into a single concept.

Not sure if you'd call that a git replacement, but it's a displacement of sorts - the function of git is replaced by non-git.

pbiggar··on Conclusions from analyzing Y Combinator’s investing history
2012 I think. There's a place existing founders can go to recommend people.

Which is probably why YC is so homogenous.

pbiggar··on Randomize HN: Removing the vote threshold for getting to the front page
It feels like using the homepage traffic to validate /new has a lot of promise, and maybe some tweaks could solve the problems you had. One idea I had from reading your comments and dan's article is to have a permanent slot on the homepage with something from /new in it.

I think you could address the issue that "readers reacted negatively, even violently, to seeing junk on HN's front page" by making it clear with a special visualization, that this slot is special. You could also add a "report low quality" button which would make that story less likely to appear in the random slot in the future.

You could even add a "show me another" which fetches another random story instead.

So roughly:

- somewhere near slot 5 we add a special "new" slot, visually identified as such

- on each page load, the slot is given to something randomly posted in the last 8 hours

- the slot is different for each request/user, so everything on new gets seen a little bit

pbiggar··on SQL Murder Mystery
I saw an unhexed answer in the original datasette link.
pbiggar··on SQL Murder Mystery
Be warned that there are spoilers built into the DB, if you look too closely. The trigger on the solution DB has the answer built into the SQL, as I learned when I ruined the game for myself.
pbiggar··on Ask HN: What are successful projects that started as prototyped hypotheses?
Dark (https://darklang.com) was a bit of both. I spent several years thinking about the problem, and once I had a solution and decided to work on it, went into rapid prototyping to figure out if it could work. To a certain extent, we're still in that phase, just with a much bigger team now.
pbiggar··on Who cares about functional programming?
Completely agree. There are a couple of "killer features" of functional programming that led to us adopting it both to build Dark, and for Dark itself. Immutable values makes it so much easier to reason about programs. And then removing null and exceptions.

The downsides: a bit of a learning curve for programmers used to OO; some classes of problems are easier with OO, though not as many as you'd expect.

The real downside I've seen is that so much valuable information is in academic papers that aren't approachable.

pbiggar··on The Hippocratic License
I remember a Douglas Crockford (the "JS: the good parts" author) talk where he had added a similar clause to the license for jslint. It said it couldn't be used for evil. And then IBM asked for an exemption.

https://en.wikipedia.org/wiki/Douglas_Crockford#%22Good,_not...

pbiggar··on Concerning ‘Remove Richard Stallman’
> Not sure that's fair. In the conclusion he writes:

I feel confident with my assessment. He showed no indication that he understood the current movement to hold powerful men accountable for their actions. For example, where's the due process for the women Stallman excluded by his horrible behaviour for decades?

Stallman went down for being a creepy perv for decades. He should have gone down for one of the many lines he crossed before today. Eventually, when you give a creep enough passes he'll say something so creepy it's indefensible, Yet here you are trying.

pbiggar··on Concerning ‘Remove Richard Stallman’
Right! There's millions of injustices in this world and you're fighting for a misogynist who has pushed women out of tech for decades? What are your priorities?
pbiggar··on Concerning ‘Remove Richard Stallman’
The author expects people to fully understand stallmans world view and to thoroughly examine his position.

However, the author did not pay the same regard to Salam G., the author of the original post reporting on the most recent of Stallmans shitty proclamations. The author shows no sign of understanding why it's important that Stallman was fired, nor did he show he had done to work to try and get it.

You can safely ignore this. I came away worse for having read it.

pbiggar··on Show HN: Darklang
There aren't any languages that support what we need to do to solve the complexity we want to solve, including OCaml/ReasonML.

Given that, whatever language we'd pick we'd have to hack them to get what we needed, and then we wouldn't have JS (realistically, if we were to pick some existing language it would have to be JS), we'd have some shitty version of JS.

Which is what App Engine did with their early versions: I worked on an app engine project that had a hacked version of Django where nothing worked.

pbiggar··on Show HN: Darklang
Great suggestions, you'll be happy to know many of these are on the roadmap, and some have already been done!

> Have multiple projectional views of the system,

Some amount of this works already (you can see callers and callees, you can see the DB schema); we want a callgraph view for sure, and I like the idea of seeing the handler at the bottom of the call stack.

> Easy example based testing

Yes, this is planned to work similar to traces, and it should be trivial to turn a trace into a test

> History of each function,

Yup, planned

> 'diff' of a snapshot against another one is great.

Planned, but low on the priority list compared to the other stuff you've mentioned.

> Annotations

Planned. We've implemented some grouping (similar concept but obviously different use cases to tagging). Some of these annotations would be automatic or semi-automatic.

> A standard CRUD UI for DBs

Planned :)

> DB/field annotations for privacy

We plan two aspects to this. There is the "PII indicator" which says this is PII and shouldn't be logged at all. Then there's access-control lists where we decide who (if anyone) can view certain attributes (eg: this dev is a contractor, do not show them live values).

Thanks for all the suggestions!

← PreviousPage 16 of 34Next →