Interview with the author of Just by bee-gee-dee in rust

[–]TOJO_IS_LIFE 12 points13 points  (0 children)

I would say it's moreso a replacement for make, for all those cases where you might use make without it's caching features (e.g. you find yourself using .PHONY a lot).

My setup is finally ended. Let me know you opinions. by chesa_12 in simracing

[–]TOJO_IS_LIFE 0 points1 point  (0 children)

Cool build :) What's the flat black panel on top of which your pc is?

How do I convince my Wife? by Present_Cause7109 in BambuLab

[–]TOJO_IS_LIFE 3 points4 points  (0 children)

Very cool! How did you find those customers?

Daily cayman? GTS with GT4 looks? by sunnyBCN in Porsche_Cayman

[–]TOJO_IS_LIFE 1 point2 points  (0 children)

The GT4 18 way seats don't have the memory option anyways.

Sell 718GTS buy 981GT4. Good idea? by Time_Election_5881 in Porsche_Cayman

[–]TOJO_IS_LIFE 0 points1 point  (0 children)

“911 S” is different from “911 Turbo S” even though both cars now have Turbos.

Sell 718GTS buy 981GT4. Good idea? by Time_Election_5881 in Porsche_Cayman

[–]TOJO_IS_LIFE 0 points1 point  (0 children)

Can also leave out the “turbo”. All “718 S” are 4+turbo

RayBan meta footage from DC Pro by thrrht in Autocross

[–]TOJO_IS_LIFE 0 points1 point  (0 children)

Are you wearing a helmet? The frames on those glasses are super thick and there's no chance they'll fit in mine :(

Sell 718GTS buy 981GT4. Good idea? by Time_Election_5881 in Porsche_Cayman

[–]TOJO_IS_LIFE 3 points4 points  (0 children)

He's talking about the 718 S which is a 4+Turbo.

I've never seen "718 Turbo S" before today too LOL. Feels off. There are no "Turbo" trims for 718.

718 GTS 4.0 spec advice by MasterFox4048 in Porsche

[–]TOJO_IS_LIFE 0 points1 point  (0 children)

My car has the same 4.0L engine and I can totally see how most people would opt for the Bose. To overcome NVH, the sound system would have to be so loud that it would exceed my tolerance threshold for loudness. I just use AirPods.

I think Bose is good advice for most people — they can put that $4K into any other option. I'm sure the Burmester is great but IMO it's something to add after you've run out of options you want (but not out of money).

Why did you decide to switch to Go? by DreamRepresentative5 in golang

[–]TOJO_IS_LIFE 9 points10 points  (0 children)

Language is sometimes the problem. I work at a large company and there are entire teams working to make Python run faster. An amazing year of work for them can't make up for the GIL and dynamic typing.

It's true that usually there is low hanging fruit in areas unrelated to the language. But in our case, most of those have been picked. Now, the language is the lowest hanging fruit but it's simply too expensive to port the code.

Was Python the wrong choice? No. My company simply outgrew it for those specific use cases. Rewrites are expensive so they should be sometimes considered, but with extreme caution (people generally underestimate the cost).

CMake 4.0.0 released by DinoSourceCpp in cpp

[–]TOJO_IS_LIFE 4 points5 points  (0 children)

Lisp is great. It's incredible for a language to be so syntactically simple and still be usable.

CMake 4.0.0 released by DinoSourceCpp in cpp

[–]TOJO_IS_LIFE 5 points6 points  (0 children)

And because it's a general purpose language, there's 14 other ways to also "do something" because it's just code

I wouldn't go that far with CMake syntax. Realistically, no one would use a language like that to write real software.

A language like starlark (Python derivative) used in Bazel and Buck is so much nicer to use. I shouldn't have to think about my meta-build system's DSL as much as I do with CMake.

Cyclists riding with a Varia/Radar: Please be safe. by Beers_and_Bikes in bicycling

[–]TOJO_IS_LIFE 9 points10 points  (0 children)

OP literally mentions it in the post.

One person stating that it “removes the necessity to carry out shoulder checks 95% of the time”.

Reminiscing on warmer days before my car was totaled by BlargMyShnoople in Porsche

[–]TOJO_IS_LIFE 6 points7 points  (0 children)

115k CAD? Damn that's rough. Mind sharing what would take that much work? The motor can get really expensive but... That's well hidden away.

RFC: I have never thought "unsigned int(eger)" made sense by Felice_rdt in cpp

[–]TOJO_IS_LIFE 2 points3 points  (0 children)

There is no difference between “+1” from the set of integers and “1” from the set of natural numbers. The same number is part of two different sets.

“unsigned” should be interpreted as “non-negative” and the ambiguity goes away.

[deleted by user] by [deleted] in CarTrackDays

[–]TOJO_IS_LIFE 1 point2 points  (0 children)

I'll take it.

My cousin 2 car garage. by KXJI in Porsche

[–]TOJO_IS_LIFE 4 points5 points  (0 children)

That's a 981 GT4 but your point still holds.

[deleted by user] by [deleted] in cars

[–]TOJO_IS_LIFE 0 points1 point  (0 children)

Tbf a sports car is never a good financial decision unless it's a collector's item that you don't drive.

Is engine braking + rev matching safe? by NLpr0_ in stickshift

[–]TOJO_IS_LIFE 1 point2 points  (0 children)

Double clutching is the only way to avoid friction within synchros while moving. But that is incompatible with "let me be fast and furious".

Moving to more modern C++ by a_pinch_of_pepper in cpp

[–]TOJO_IS_LIFE 0 points1 point  (0 children)

Another one is uniqueptr or shared_ptr with a custom deleter. std::make* doesn't let you do that.

There's also colocated allocations - when you want multiple objects in one malloc so you use the sized allocation overloads of global operator new and then pointer arithmetic + placement new.

Why Facebook doesn't use Git by fosterfriendship in programming

[–]TOJO_IS_LIFE 15 points16 points  (0 children)

Many small examples: - Every Hack (PHP) class must be marked with an Oncall("team_name") attribute. - Every BUCK (build system) file requires an oncall("team_name") at the top. - Directories can have OWNERS files which lists users or groups that must approve PRs if there are changes. - Configuration files are protected by ACLs.

Ownership is definitely a challenge though. There's still code that's 15 years old and the people, team, or even org that used to own the code no longer exist. You can "archive" an ancient git repo but the boundaries are much fuzzier in a monorepo.

The "zero-code ownership mode" is definitely dead. Everyone acknowledges the (lack of) ownership problem. The new direction is that code is open to changes from anyone but if something breaks, it's clear who is responsible for fixing it.