sorted by: new top controversial old
1
DBOS Cloud: A transactional serverless computing platform with first-class TypeScript environment (www.dbos.dev)
 

DBOS Cloud, a transactional serverless computing platform, made possible by a revolutionary new operating system, DBOS, that implements OS services on top of a distributed database. We’ve used this new architecture to build a novel TypeScript transactional programming environment that enhances applications with automatic statefulness, transactionality, observability, and cyber-resilience. This makes fault-tolerant cloud-native application development much simpler and faster.

1
GitHub - lorefnon/collection-joiner: Type-safe utilities to join multiple collections from different sources into a single hierarchy (github.com)
 

When developing APIs or writing integration solutions, we often fetch data from multiple sources and combine them together. This requires quite a bit of boilerplate even if you use utility libraries like lodash.

This library aims to be provide a simple type-safe utility that makes the task of combining multiple collections simpler using an intuitive association API.

You may find this API to be reminiscent of association APIs found in ORMs. However, collection-joiner is completely agnostic about how these collections are obtained - so you could for example, fetch a list of users from a database, a list of departments from another service, a list of roles from a key value store and merge them into a single hierarchy when constructing a response.

What do y'all think about mailing lists and IRC as sole communication channels? in c/programming@programming.dev
Some *real* benchmarks on Bun (compared with Node) -- It only wins *sometimes*, but it's mostly a fail in c/programming@programming.dev
[–] 6 points 2 years ago

Build times in nodejs are not so great in even medium size projects if you make heavy usage of advanced typescript features - either yourself or through libraries like zod. So if something makes the nodejs runtime faster, it could potentially make ts compiler faster too - for which I'd be very grateful.

  • permalink
  • fedilink
  • source
  • parent
  • context
    • What is the best file format for configuration file? in c/experienced_devs@programming.dev
    2
    RSS Feeds blocked on AWS ? (programming.dev)
     

    I am unable to subscribe to RSS feeds for programming.dev from a yarr instance hosted on an AWS EC2 instance (ap-south-1).

    This issue seems specific to programming.dev. I can access RSS feeds for other lemmy instances without any issues.

    I can access the feeds from browser, but when I try to fetch it on AWS I get a 403 error. Curious if this is done intentionally.

    $ wget https://programming.dev/feeds/c/programming.xml?sort=Active
--2023-07-17 18:27:15--  https://programming.dev/feeds/c/programming.xml?sort=Active
Resolving programming.dev (programming.dev)... 172.67.137.159, 104.21.73.21, 2606:4700:3031::ac43:899f, ...
Connecting to programming.dev (programming.dev)|172.67.137.159|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2023-07-17 18:27:15 ERROR 403: Forbidden.
    Is anyone migrating from Java to Kotlin at work? in c/programming@programming.dev
    [–] 1 point 3 years ago

    I don't use it right now, but two years ago I helped a team incrementally adopt Kotlin in a ten year old java/spring/mybatis codebase. We didn't have any android experience and in the initial few months mostly used kotlin as a better java, avoiding features that would prevent us from switching back to java if needed.

    But it worked pretty well - we didn't face much resistence from people experienced with java because they could still continue to benefit from their jvm familiarity, and the language was approachable to new folks who joined us. It also helped that we could just copy paste java code into a .kt file and intellij would convert it to kotlin.

    We didn't venture into kotlin's js/native targets but for jvm it worked out great for us.

  • permalink
  • fedilink
  • source
    •
    view more: next ›