jtregunna

Just an investigation and deep dive from first principles.

In what sense? The phrasing is just a generalization, production-grade anything needs consideration of the needs and goals of the project.

Right, you do need to fsync when creating new files to ensure the directory entry is durable. However, WAL files are typically created once and then appended to for their lifetime, so the directory fsync is only needed at file creation time, not during normal operations.

Update:

I updated the post based on the conversation below, I wholly missed an important callout about performance, and wasn't super clear that you do need to wait for the completion record to be written before responding to the client. That was implicitly mentioned by writing the completion record coming before responding, but I made it clearer to avoid confusion.

Also the dual WAL approach is worse for latency, unless you can amortize the double write over multiple async writes, so the cost paid amortizes across the batch, but when batch size is closer to 1, the cost is higher.

Post talks about how to use io_uring, in the context of building a "database" (a demonstration key-value cache with a write-ahead log), to maintain durability.

Actually, this is exactly why Canada should be looking for other markets. The US has clearly indicated to us that we can no longer rely on them for trade. It's long overdue, but now is the time we need to act in reducing our dependence on the US, since clearly one dumbass can impact our economy in ways that one dumbass shouldn't be able to.

> Secret courts are a shame. Secret directives, on the other hand, can be compatible with the rule of law and an independent judiciary, provided they're lawfully authorized and can be challenged in a court.

I presume you also forgot to add this before challenged in a court...

> ..., whistleblowers are protected, and can be ...

You see, because that's the thing with secret directives, they're redacted from the public eye. The only way we get visibility into them isn't with FOIA requests, it's with whistleblowers who feel the government is doing things wrong, and if they're not protected, they rarely come forward.

Textbook nonsequiter, well done.

Uh, not my intent. I'm trying to illustrate that Canada has command and control regulations regarding telecommunication providers that operate in the country, and there are requirements for Canadian control. If equipment were factored into such decisions, that could go a way into resolving this problem. Though it'd probably create others. And for completeness, it's still Canada's decision to make, the rhetoric the US has been sending our way has left many of us feeling like the once good friend and neighbour, has decided that we're a threat to their national security.

EDIT: Clicked too soon.

Sure, doesn't hurt to listen, but at the end of the day, that's just being polite. A courtesy. The decision is still entirely Canada's, and shouldn't be influenced by US congress critters.

Sure, just saying, Canada should review any orders it makes towards telecom companies (full disclosure, I started and ran a telecom company from 2001 until 2010) from entirely a Canadian perspective and not account for any input from the US; doubly so given how the US government (like it or not, Trump is their president and reflects their government internationally) has treated Canada over the last year and a half.

> As a Canadian citizen, I urge Canada to snub Huawei too.

I'm not a fan of Huawei, but I am a fan of retaining our sovereignty. If the US wants the privilege of suggesting how we should run our country, then perhaps they should work on their end to repair the bilateral relationship. Currently, my vote is to tell them "Mind your own damned business."

Oh I know it can, my comment was more tongue in cheek not dismissive :)

It's almost always more efficient to use an existing CPU if it fits your use case than to design your own. Even if it doesn't, it is often more efficient (time wise) to adapt your use case to the hardware you have available, or write software to resolve the feature you want in hardware but don't have. Only the especially nutty build their own CPUs (I'm especially nutty too)

More likely referring to the fact that Dropbox has had many an issue lately of doing things that may not have been intended to look nefarious, but look that way nonetheless. This is just the last straw for some users, whether or not the feature was used by them.

And where exactly would it drain to? Your toilet's output is plugged, thus causing the overflow, remember?

Go is one of those languages I'd like to use more, but can't find a good fit for the kind of work I do (I mostly write iOS apps, and programming languages myself (weird dichotomy I know)).

What benefits does Fibur give you that em-synchrony doesn't? Not suggesting there isn't a need for a competitor, but trying to place it in the space.

Agreed, free forming is great for 1 person projects.

My family has been in what is now Canada since not long after our family was forced out of Scotland by the English. I myself am 7 generations removed from immigration.

I like the analytics bitly gives. Noted for the future.

Funny, I recall billing one of my last clients significantly more than almost zero to develop an app for them. Apps cost real money to build, and real money to maintain.

How about "all of the above"? Various projects have various needs, some more than one, which means you typically end up with lots of different databases.

I like the Canadian system of software patents. CIPO requires that software may only be patented in so far as the hardware it runs on is unique and patentable. I'm ok with those under the condition that the entities who hold the patent actually do something with it. Explicit timeframes should be in place to prevent these types of "business models" over long periods.

I'm sorry, but there's something to be said for a good article. A good article isn't one whose first two sentences are flame bait. As such, I couldn't read the rest of the article.

Yeah it's certainly not limited to "superstar", it just strikes me as odd and I'm not exactly sure why it's used so often.

I mean I am well aware that finding good developers is hard (always has been), but now, when it's hard to find developers who can deliver period, resorting to ego stroking this early on? Can't be a good thing.

News will get around if there's no money to be had for future projects. That said, don't focus on the bubble, focus on your ideas. Distractions kill.

Best advice I can give you is to approach local individuals and organizations who are more likely to support your project (Google has offices in Kitchener, for example, some other local companies are very visible in the open source community; one notable company is Waterloo based PostRank, visible in the Ruby community). Talk to people, and be up front with what you're looking for.

What's the worst that can happen? Someone can say no. If that's your biggest problem, you're golden. There are a lot of people who would be willing to talk to you about this.

Best way I've found is to start out on hourly gigs, until you have a sense of how long certain tasks take you. With experience, you get better at estimating your time.

EDIT: Oh and when you start out, if you're estimating time, double it.

Due to lack of any good metrics, I always take all "Review my startup" links with a grain of salt. I try and keep note of the ones that look interesting, but generally after perusing the site, I forget about it. Some are downright ridiculous, others look interesting. There's an opportunity here somewhere, I just don't see it. :)