devmunchies

This might give businesses the ammo they need to require the employees to come into the office.

Am curious about QUIC and HTTP3 as well.

If the startup is tiny (less than 10) then I would give the benefit of the doubt to the company. At that size, it’s mostly tapping your network and not having any full time recruiters who can prioritize things other than “I need somebody, anybody! Help!”

Another analogue would be dating. It’s hard to network or build a lasting relationship with people you’ve never met in person.

I prefer working in person so from my PoV requiring RTO is pro-worker.

> The only group not benefitting from RTO are the actual workers.

That depends on the worker’s goals. If your goal is to have work/life balance or “personal” productivity then, yeah, I empathize. But there is more investment I put back into my team when I’m in person. It’s not just my code output. I find it very hard to mentor young engineers remotely.

Also, if you are a stockholder, like many engineers, and if teams do in fact have more “synergy” (bleh) then it’s also good for the workers via stock based comp.

It just depends on how you are using the JSON and where it fits in an application. If I'm using a static language, it is common for me to have a TimeSpan (or similar) type and standard rules for how it can be serialized (e.g. toString, toJson, etc). In this scenario, I don't care how it is represented in JSON, I just want convenient (de)serialization.

With your example, I would need to create custom parsing logic, and handle a dynamic number of JSON fields. But if a TimeSpan class had JSON deserialization built in based on the ISO8601 format, then I wouldn't need to do anything special. That's the benefit of using the standards. Same if I wanted to convert the JSON stringified format into a postgres time span there isn't any special parsing logic I need to do.

Yes, it's just a string in JSON, so it's not semantically special. But other languages that have a TimeSpan type could take advantage of the standard serialized format.

Here is an example of what it could look like in F#, no special logic for deserializing into a custom type:

    type MyEvent = {
      myDuration: TimeSpan;
      createdAt: DateTimeOffset;
      eventId: string;
    }

    let rawJson = 
      """
        {
          "myDuration":"P15DT5H0M20S",
          "createdAt": "2023-08-24T20:30:00Z",
          "eventId": "e_1234"
        }
      """
      
    let myEvent = JsonSerializer.Deserialize<MyEvent>(json = rawJson)

An often ignored part of the standards are how to represent durations (time spans).

See http://xml.coverpages.org/ISO-FDIS-8601.pdf (section: 5.5.4.2 Representation of time-interval by duration only, pg. 21)

Would like to see more json parsers in static languages allow me to define a field as a time span and can serialize into the valid format.

For an example, see this proposal in Crystal: https://github.com/crystal-lang/crystal/issues/11942

    Example:  A duration of 15 days, 5 hours, and 20 seconds would be:

      P15DT5H0M20S

    A duration of 7 weeks would be:

      P7W

I actually used this in my F# code yesterday. The forall function does the same and it was exactly what I needed.

https://fsharp.github.io/fsharp-core-docs/reference/fsharp-c...

> You are referencing untested hypothetical challenges against laws you disagree with

An assumption. I also didn’t say whether the 2nd amendment laws were illegal or wrong.

Then many states are also violating the 2nd amendment by requiring an ID or gun safety card.

> simply because I feel more comfortable and relaxed at home

this core preference in environment and vibe is the main difference between the 2 camps. I was desperate to be in an office where there was a buzz of high energy and a go, go, go environment like skydivers jumping out of a plane. Would still prefer a private office though so get deep focus when necessary.

Not sure if its nature or nurture, since I grew up doing team sports year round.

Which is weird because google has a partnership with replit, unless replit has a hand in this project. If not, pretty ruthless.

funny, the reason i say its not battle tested is because of an issue i discovered in the extension system that was mentioned in that post.

I personally found a glaring performance issue in the library related to plugins and created a github issue for it back in December (I don't think it's been fixed to date). I was confused because it was pretty obvious. "Battle tested" things, by definition, have been through battles and don't have as many easy pickings on optimizations.

I wouldn’t consider htmx “battle tested”.

Musk isn't the CEO. I doubt this is the CEO's decision.

Yeah most likely just french translation. A more accurate translation would have been "from" in this context.

`js_from_ocaml`, `string_from_int`, etc would have been clearer in english.

If i didn't speak Spanish it would bother me a lot more.

You can subscribe to all topics by using a *. Why not have a debug subscriber that listens to all messages and plays it in the terminal?

I agree that the auth system is cumbersome. I wanted to use it on the edge for IoT devices where the device only has the same permissions as the user who the device belongs to, but not very easy. Their auth isn’t very customizable.

> profoundly better

How? Better/newer algorithms? Faster? Cleaner code? Better APIs?

How does one compile a language to other architectures which are not “officially” supported? It should be doable since it uses LLVM? Example, ESP32 SoC.

Nice! We don’t use Go though :) we use F#, Rust, and C.

Would love to see this work supported by the core Nats team. A standard spec so others could make clients.

Yeah completely different tech but it can solve the same problem—connection and communication between services. Implementation details.

If you don’t think about the tech between services, at the end of the day my service is using some protocol to send and receive data, using grpc or otherwise.

NATS has a clean request/reply paradigm built in that makes this simpler.

I prefer another CNCF incubating project, NATS. (nats.io)

It decouples the service addresses via a pubsub architecture.

So if I want service A to send a request to service B, then it is done by subscribing to a shared topic, there is no service discovery.

It kind of replaces GRPC and Istio.

I like the “static typing” and code generation you get from grpc so a hybrid of the 2 would be my preference.

I actually solved the code generation part for NATS though by using AsyncAPI (like Open API but for messaged based systems). Would be better if baked in.

There are no motors, so more simple. There are mics, speakers, LEDs, LCDs, buttons, etc. I have a firmware engineer who also does electrical engineering, and a mechanical engineer who works with manufacturing, compliance, and industrial design.

I come from a traditional full-stack engineering background (web frontend + backend) and recently founded a smart toy company[1], the first product built on ESP32-S3. I took a few weeks for me to get comfortable writing firmware (although there is another more experienced engineer doing the primary work and electrical).

I'm really excited for Espressif (the chip maker) to roll out newer versions of their microcontrollers on RISC-V. I would love to see a renaissance of inexpensive personal devices.

[1]: We're pre-launch so nothing to share now.

I never said what they are doing isn't "shitty".

I share a password manager with my spouse. There’s no way she would use it if it didn’t have a good mobile app.

> your only option

A calendar reminder to cancel the week before renewal is another option

WaybackMachine’s oldest snapshot for this url is Sept 2019.

https://web.archive.org/web/20230000000000*/https://www.jane...