pydantic-core
Laminar
pydantic-core | Laminar | |
---|---|---|
18 | 26 | |
1,280 | 716 | |
2.0% | - | |
9.6 | 8.3 | |
3 days ago | about 2 months ago | |
Python | Scala | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pydantic-core
-
Is there a pydantic.BaseSettings equivalent in rust?
Funny that you ask... https://github.com/pydantic/pydantic-core Unfortunately it seems that the functionality you ask for is not (yet) part of this ...
-
Investigating Pydantic v2's Bold Performance Claims
I encourage you to checkout the official benchmarks for more realistic and detailed examples, and, as always, YMMV.
-
Pydantic V2 leverages Rust's Superpowers [video]
> to also be constrained by a separate set of data types which are legal in rust.
This isn't really how writing rust/python iterop works. You tend to have opaque handles you call python methods on. Here's a decent example I found skimming the code.
https://github.com/pydantic/pydantic-core/blob/main/src/inpu...
-
Pydantic vs Protobuf vs Namedtuples vs Dataclasses
Thanks for pointing out to that, I did not know about it. Also attaching repo in case someone would be interested as well - https://github.com/pydantic/pydantic-core
-
Introducing CodSpeed: Continuous Performance Measurement
pydantic-core: The core validation logic for pydantic, a Python data parsing and validation library.
-
Show HN: Python framework is faster than Golang Fiber
pydandic-core [0] will hopefully solve this issue (written in Rust)
[0] -- https://github.com/pydantic/pydantic-core
- Scala or Rust? which one will rule in future?
-
Rust for Data Engineering—what's the hype about? 🦀
LinkedIn influencers are weird lol. Rust v Python is apples and oranges. Rust would be glued together by python just like it does with C/C++ and Java/Spark today. We’re already seeing some packages go this direction, like pydantic v2 is rewriting its core validation in rust.
- Python file structure with Rust extensions
- Pydantic 2 rewritten in Rust was merged
Laminar
-
Ask HN: Those making $500/month on side projects in 2024 – Show and tell
My quite niche open source project broke this threshold last year, via Github sponsorships. Of course, I put a lot of time into it, so it's not "passive income" or even "market rate income", but still, without these sponsorships I wouldn't be able to work on it so much.
The project is Laminar, a UI library for Scala.js https://laminar.dev
- The golden age of Kotlin and its uncertain future
-
Why would users avoid a library that makes heavy use of macros in Scala 3?
I've noticed that Laminar and the newly released Kyo point that they don't use a lot of macros as a feature. Laminar says "Easy to understand: no macros", while Kyo emphasizes "Note: defer is currently the only macro in Kyo. All other features use regular language constructs." It seems that using less macros is something library users will like.
-
Is there any book or course about Scala front-end development?
https://laminar.dev/ might be what you need. Though I wish there was a more beginner friendly (I'm not from front-end world) tutorial for me to follow along.
-
Designing an HTML Component system
Have you looked at Laminar and Tyrian? Especially Tyrian seems to be close to what you're looking for.
-
The Quest for the Ultimate GUI Framework
For Scala there is Laminar, which has an even flashier website with nice docs. I haven't tested it out though, as I have never used Scala.
-
Solid like scala library that has more powerful reactive primitives and lean syntax?
I found this scala library called Laminar which looks super similar to solid. They use signals and has no virtual dom. State changes are represented by signals and events by event streams. Thus they seems to have feature parity with RXJS as they can model all sorts of async stuff. Best part is they get to keep writing their markup in C-style syntax than XML based JSX. It looks super elegant,minimalist and has type safety.
-
Solid JS compared to svelte?
This is very true. I really hate svelte single file components. But then I tried JSX for breaking things down. I love solid but I don't feel really good about angle brackets within C style syntax. I saw this Scala library that stick with simple statically typed function syntax than html tags. I don't understand why people still wants to stick with xml like tags. In laminar markup is written like this scala div( h1("Hello world", color := "red"), inputCaption, input(inputMods, name := "fullName"), div( ">>", button("Submit"), "<<" ) ) I wish solid team makes their HyperScript syntax as performant as JSX.
-
Ask HN: What companies are embracing “HTML over the wire”?
Laminar (Scala framework) hasn't been mentioned yet so dropping it here as an awesome framework that support HTML-over-the-wire. It can be used together with React, HTMX, and many other frontend frameworks -- but doesn't have to be.
https://laminar.dev/
-
10 Years of Scala.js
Scala.js core itself, which I maintain, does not need much innovation. We support all of Scala, and interact with any JavaScript library. That's what the core promises.
If you want to compare to Scala 3, it's worth pointing out that you can use Scala.js with any Scala version >= 2.12.2. In particular, you can use it with Scala 3 and benefit from all its innovations. ;)
Innovation comes mainly from libraries, notably UI libraries. Laminar (https://laminar.dev/) is a great example.
In terms of roadmap, we are mostly working on "boring" stuff: improving performance (of the generated code, and of the linker), fixing bugs when they get reported, etc.
Perhaps, when Wasm gets more features for deeper interoperability with JavaScript (manipulating objects notably), we will take another look at targeting Wasm. People usually expect all languages to target Wasm now, "because it's fast". Truth is, it's fast for languages with linear memory. There is no evidence yet that it will be fast for memory-managed languages with objects and virtual dispatch.
What are some alternatives?
aiohttp-apispec - Build and document REST APIs with aiohttp and apispec
OutWatch - The Functional and Reactive Web-Frontend Library for Scala.js
msgspec - A fast serialization and validation library, with builtin support for JSON, MessagePack, YAML, and TOML
tyrian - Elm-inspired Scala UI library.
pymartini - A Cython port of Martini for fast RTIN terrain mesh generation
Binding.scala - Reactive data-binding for Scala
koda-validate - Typesafe, Composable Validation
Udash - Scala framework for building beautiful and maintainable web applications.
modin - Modin: Scale your Pandas workflows by changing a single line of code
scalajs-react - Facebook's React on Scala.JS
typedload - Python library to load dynamically typed data into statically typed data structures
slinky - Write Scala.js React apps just like you would in ES6