Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
InterfaceSpecs.jl Alternatives
Similar projects and alternatives to InterfaceSpecs.jl
-
-
RequiredInterfaces.jl
A small package for providing the minimal required method surface of a Julia API
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better InterfaceSpecs.jl alternative or higher similarity.
InterfaceSpecs.jl reviews and mentions
Posts with mentions or reviews of InterfaceSpecs.jl.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-19.
-
Julia as a unifying end-to-end workflow language on the Frontier exascale system
I don't really know what kind of rebuttal you're looking for, but I will link my HN comments from when this was first posted for some thoughts: https://news.ycombinator.com/item?id=31396861#31398796. As I said, in the linked post, I'm quite skeptical of the business of trying to assess relative buginess of programming in different systems, because that has strong dependencies on what you consider core vs packages and what exactly you're trying to do.
However, bugs in general suck and we've been thinking a fair bit about what additional tooling the language could provide to help people avoid the classes of bugs that Yuri encountered in the post.
The biggest class of problems in the blog post, is that it's pretty clear that `@inbounds` (and I will extend this to `@assume_effects`, even though that wasn't around when Yuri wrote his post) is problematic, because it's too hard to write. My proposal for what to do instead is at https://github.com/JuliaLang/julia/pull/50641.
Another common theme is that while Julia is great at composition, it's not clear what's expected to work and what isn't, because the interfaces are informal and not checked. This is a hard design problem, because it's quite close to the reasons why Julia works well. My current thoughts on that are here: https://github.com/Keno/InterfaceSpecs.jl but there's other proposals also.
- Formal specifications and static checking of interfaces in Julia
- Composable static typing and formal verification for Julia
-
A note from our sponsor - InfluxDB
www.influxdata.com | 6 May 2024
Stats
Basic InterfaceSpecs.jl repo stats
3
55
5.7
7 months ago
Keno/InterfaceSpecs.jl is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of InterfaceSpecs.jl is Julia.
Popular Comparisons
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com