Elixir
proposal-ptc-syntax
Our great sponsors
Elixir | proposal-ptc-syntax | |
---|---|---|
133 | 7 | |
23,003 | 164 | |
2.3% | 0.0% | |
9.9 | 0.0 | |
7 days ago | almost 8 years ago | |
Elixir | HTML | |
Apache License 2.0 | - |
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.
Elixir
-
Perfect Elixir: Environment Setup
I’m on MacOS and erlang.org, elixir-lang.org, and postgresql.org all suggest installation via Homebrew, which is a very popular package manager for MacOS.
-
Top Paying Programming Technologies 2024
6. Elixir - $96,381
-
Meet entr, the standalone file watcher
As you might have guessed, one of the main use cases for entr is to rerun tests whenever files change. I'm an Elixir engineer, and I use entr to run mix test continuously whenever I save an Elixir file.
-
Building Apps with Tauri and Elixir
The Elixir programming language is no stranger to desktop applications as the language actually supports building them out of the box. It uses wxWidgets: a C++ library that lets developers create applications for Windows, macOS, Linux and other platforms with a single code base. But wxWidgets has a very complex API, and doesn’t solve issues that usually come with desktop applications around packaging.
-
Show HN: Podsee – AI tool for podcast listeners
Hi everyone, I just launched Podsee(https://pods.ee) for podcast listeners, lovers. You can search and listen to podcasts at Podsee. What makes it different is that you can get the AI transcript for an episode.
It started as a side project after I resigned my job one year ago. As a programmer, I love Elixir (http://elixir-lang.org/) and Phoenix LiveView(https://github.com/phoenixframework/phoenix_live_view), and want to make a product with it. So I build Podsee.
I'm planning to add more AI features to it, like summarize the episode audio, episode to comics, etc.
I'd love to invite you all to try out the product and would appreciate hearing your feedback! Thanks!
-
A Linguagem Lua completa 30 anos!
Elixir, criada por José Valim, egresso da USP (Engenharia Poli-USP) https://elixir-lang.org/
-
Programming Languages Every Developer Should Watch Out For
4. Elixir
-
Lightweight dev tools.
Sadly, this isn't true for all languages. I spend most of my days working on and with the Ash project in Elixir. Whilst Lapce has syntax highlighting for Elixir there is no language server plugin available yet. There are at least two plugins in development, but given I can't figure out how to install them in my local editor to test them I can't speak to their quality.
-
Elixir for Cynical Curmudgeons
> if is a macro.
> def is a macro.
> defmodule is a macro.
> It’s all macros. It’s ALL MACROS! ALL THE WAY DOWN! AAAAAAAAAA AHAHAHAHAHHAHAAAA!
Also see the definition for `defmacro`, the macro for defining macros, which is defined using... defmacro
https://github.com/elixir-lang/elixir/blob/v1.15/lib/elixir/...
-
Meta to release open-source commercial AI model
Career dev who had the cash and wanted to experiment with anything that can be done concurrently, such as in my language of choice lately, which features high concurrency (https://elixir-lang.org/) or these LLM's, or anything else that can be done in massively parallel fashion (which is, perhaps surprisingly, only a minority of possible computer work, but it still means I can run many apps without much slowdown!)
I originally had 2 2080ti's to experiment also with virtio/proxmox (you need 1 for the host and 1 for any VM you run). I never got that running successfully at the time, but then Proton got really good (I mainly just wanted to run windows games fast in a VM, but that circumvented that). Later on I upgraded one of them to a 3080ti.
It's a System76 machine, they make good stuff
proposal-ptc-syntax
-
Bun, JavaScript, and TCO
This is not actually about Tail Call Optimisation, which is more flexible and optional matter of optimisation, but about Proper Tail Calls, which are actually part of the ECMAScript 6 specification (over implementer objections)—in strict mode, calls in tail position must not create additional stack frames. This is the last piece of ECMAScript 6 that most engines haven’t implemented, because it’s rather controversial: it actually causes some performance problems, and makes debugging harder, and may have security issues (in 2016, Mozilla declared it impossible to implement across realm boundaries due to their security model).
https://github.com/tc39/proposal-ptc-syntax has a lot of useful information about it all, and a proposal to make it explicit in syntax, such as with `return continue …`.
(Fun terminology problems here. The term TCO is commonly used for PTC, and PTC is very close to being a subset of TCO, but the mandatory stack frame elision which ruins debugging feels to me like it falls outside of TCO. In various situations, debuggers will mark things like “stack frame omitted” when they’ve optimised one out of existence, but you can generally compile things differently, or something like that, to prevent this. But with PTC, it feels like the engine is kinda not even allowed to know that a stack frames may be absent. So I say PTC and TCO are a little distinct, though PTC is mostly just a subset of TCO. Reminds me of the terminology of tree-shaking versus dead code removal—where the former is essentially a subset of the latter, but that the effects are just slightly different, though I’d say it’s more slight in that case than this.)
-
Show HN: We are trying to (finally) get tail-calls into the WebAssembly standard
4. Proposed something else [ https://github.com/tc39/proposal-ptc-syntax ]
While apple is against Syntactic tail calls, they’re mainly just opposed to versions of it that would remove/unrequire the tail-call optimisation they already do: https://github.com/tc39/ecma262/issues/535
For the version of it that is backwards compatible, they wouldn’t need to do anything other than recognise it as valid syntax. Their main concern is that it "could add confusion with very little benefit."
-
What happened to proper tail calls in JavaScript? (2021)
from the linked PTC proposal in the article (https://github.com/tc39/proposal-ptc-syntax):
> Unfortunately, the TC39 process at this time did not require heavy implementation involvement and so while many implementers were skeptical, the feature was included and standardized as part of ES6.
The spec for STC has a critique of PTC:
- performance
- developer tools
- Error.stack
- cross-realm tail calls
- developer intent
See: https://github.com/tc39/proposal-ptc-syntax#issues-with-ptc
Apple's 2016 response as to why they won't implement STC is here: https://github.com/tc39/ecma262/issues/535
- STC is part of the spec and will take too long to change.
- Now that they've implemented support for PTC, they don't want to regress web pages that rely on it.
- They don't want to discourage vendors from implementing PTC by agreeing to STC.
- They don't want to introduce confusion.
Some of these arguments about confusion and delays seem wrong hindsight, since on every point things would have been better if they'd just agreed to the compromise of STC.
- It would have been part of the spec years ago
- STC would have had a clear way for web pages to know when tail calls could be relied on (and PTC would have been optional)
- Other vendors didn't implement PTC in any case, despite no agreement on STC
- There's even more confusion as things are now
-
@lrvick bought the expired domain name for the 'foreach' NPM package maintainer. He now controls the package which 2.2m packages depend on.
You can see a direct example of this with Proper Tail Calls (PTC). It was added to the ECMAScript spec in 2015 as part of es6, but as of today - 7 years later - only Safari has shipped it*. As a result it is effectively not a thing in JavaScript, and the followup proposal meant to address issues with PTC ("Syntactic Tail Calls") has been basically ignored because PTC is already in the spec.
-
Node.js 14 is over 20x faster than Python3.8 for fib(n)
V8 implemented tail call optimization in the past, and the V8 team backed the TC39 proposal for syntactic tail calls (where you'd write return continue func() to make the use of TCO explicit). In Node 6 and 7 we could use them with the flag --harmony-tailcalls. The feature was removed from Node 8 after that proposal didn't go anywhere, but it's interesting, and shows some interest.
What are some alternatives?
rust - Empowering everyone to build reliable and efficient software.
solidity - Solidity, the Smart Contract Programming Language
crystal - The Crystal Programming Language
rust - Rust for the xtensa architecture. Built in targets for the ESP32 and ESP8266
Akka - Build highly concurrent, distributed, and resilient message-driven applications on the JVM
React - The library for web and native user interfaces.
Phoenix - Peace of mind from prototype to production
nx - Multi-dimensional arrays (tensors) and numerical definitions for Elixir
scala - Scala 2 compiler and standard library. Bugs at https://github.com/scala/bug; Scala 3 at https://github.com/scala/scala3
actix - Actor framework for Rust.
lunatic - Lunatic is an Erlang-inspired runtime for WebAssembly
phoenix_live_view - Rich, real-time user experiences with server-rendered HTML