misframer

What do you mean by "mission of self-service still hasn't yet been proven"?

I mostly use an M1 iPad Pro for personal use. I can get 90% of my personal work done on it, but not everything (e.g. I had to use my laptop for some tax filing work).

GitHub Codespaces works well enough to work on my blog but it’s not a replacement for the full dev environment I have on my laptop.

If you just had to pick one, I would go for the MacBook Air.

Their jobs pages (e.g. [0]) mention "ScyllaDB/Cassandra".

[0] Senior Site Reliability Engineer: https://discord.com/jobs/4004051002

They brought it back[0]. I remember getting discounts for lattes and mochas.

[0] https://stories.starbucks.com/stories/2021/starbucks-brings-...

iPhone and iPad have replaced almost all of my personal computing needs. I still use a MacBook for a DAW to play guitar. I am traveling these days and the MacBook stayed home.

My work laptop is now an M1 MBP. It's working out fine (after a few Docker hiccups).

Yes, both for personal projects and at work. I write APIs in Go (and there's React on the UI side that talks to it). I use VS Code to develop and build as a Docker image.

At work the images are deployed on DC/OS, and for my personal projects I use Docker Compose.

The most difficult part (which isn't really that difficult) would probably be the actual deployment part, and that's not specific to Go.

I use Fastmail with a personal domain name.

Here’s the email I got from Tastyworks:

> Apex Clearing, who acts as the custodian of all tastyworks accounts, has informed us that the following symbols (AMC, GME, & KOSS) will be set to closing only order status immediately. You will only be able to submit orders to close out any open positions that you have in these symbols.

> New opening orders will not be accepted at this time. We will update our clients should the clearing firm lift the Closing Only status in the near future.

I don't think they use Apex anymore.

https://blog.robinhood.com/news/2018/10/9/introducing-cleari...

Apex is the clearing firm for Tastyworks and Webull too. I got an email from Tastyworks about restrictions (which just got lifted).

I switched from Simple to Ally a few years ago and had 0 problems. I recommend them all the time.

Can you explain more about the encryption process?

Try writing an interpreter! “Make a Lisp“[0] and Norvig’s “(How to Write a (Lisp) Interpreter (in Python))”[1] really helped me understand the basics.

[0] https://github.com/kanaka/mal

[1] https://norvig.com/lispy.html

The frames are here: https://terkelg.github.io/zuckerberg.smile/assets/sprites.jp...

What do you mean by area? Geographic location or technical?

Separately. I haven't updated it to use the plugin. Thanks for Caddy, BTW!

Thanks! Yeah, will look into a CDN or just hosting it from an S3 bucket.

I’m using Hugo and Caddy. It’s running out of file handles.

Author here. Sorry, resizing my droplet now.

Great post! I started writing a Lisp interpreter in Go with the mal guide but switched to Norvig's (How to Write a (Lisp) Interpreter (in Python)) [0] since it was more approachable (IMO) as a Lisp beginner. I'm looking forward to writing a compiler next like the author.

[0] http://norvig.com/lispy.html

A few people I follow have left SF for NYC. I’m curious if anyone on HN has done the same and why.

These are refurbished.

This was done a few years ago. See https://web.archive.org/web/20150325003526/http://blog.found....

What was the concurrency like in those benchmarks?

> Firestore is literally built on top of spanner.

Do you have a source for this? Thanks in advance.

>> Badger provides better performance than RocksDB, both in terms of reads and writes.

> It's not that simple. It's never that simple.

Yeah. The post that is linked[0] within that quote has a "Benchmarks" section, but it looks like they're either 100% reads or 100% writes. Most real workloads aren't like that.

[0] https://blog.dgraph.io/post/badger/#benchmarks

I wrote a blog post on how to implement secondary indexes using an ordered key-value store a couple of years ago: https://misfra.me/2017/01/18/how-to-implement-secondary-inde...

It would work with FoundationDB, RocksDB, etc. I actually learned these techniques when I interned at FoundationDB but have used them the most with other K-V systems.

I think they're built on a common storage system, just like the MySQL compatible version too.

Not sure why I'm getting downvoted. The characteristics sound exactly like Aurora.

- "replicates six copies of your data across three AWS Availability Zones (AZs)" [0]

- "Amazon DocumentDB uses a distributed, fault-tolerant, self-healing storage system that auto-scales up to 64 TB per database cluster." [0]

- "When writing to storage, Amazon DocumentDB only persists a write-ahead logs, and does not need to write full buffer page syncs." [1]

[0] https://aws.amazon.com/documentdb/

[1] https://aws.amazon.com/documentdb/faqs/

Sounds like this runs on the same storage service as Aurora.