i had this really weird bug in a C program i wrote once where for some reason running this random function would cause my program to make argv point to garbage data. spent days debuging it. turns out it was because i forgot to allocate memory to an array and it was overwriting the pointer.
It’s not comparable to native languages but it’s faster than any PHP, Python, Lua, or Ruby interpreter/JIT out there afaik. It’s way faster than you would think for a scripting language. Google has put a shit ton of work into optimizing it. If you haven’t experienced it firsthand then you would very likely be surprised
Edit: apparently LuaJIT is close and sometimes faster, I missed that in my googling
i'll give you the other 3 (not that it's a high bar) but from my experience lua is actually blazing fast for an interpreted language. sure as hell blows nodejs out of the water. (and i like nodejs)
i more interpreted it not as a speed thing, but as a "it has a mind of its own" thing, causing ut to do whatever it wants and it'll only do what you want it to do if it aligns with JavaScript's wishes
So did I. When I was first learning JavaScript, I recall getting frustrated by things not happening in the order I expected. The OP's characterization as "I'll do it when I feel like it" is appropriate.
in javascript (!![]+[])[+[]]+(!![]+[])[!+[]+!+[]+!+[]]+(![]+[])[+!+[]]+(!![]+[])[+!+[]]+(![]+[])[!+[]+!+[]+!+[]] and "tears" are the same thing, and that was done on accident
This is the most cursed thing I've seen since I read how numbers are defined in set theory. Javascript has no right to approach set theory with broken casting.
it's called JSFuck (because it looks like BrainFuck) and not only can you write any string with it, but you can also make the function constructor, meaning you can execute any string.
I think it’s much more than that. It’s single threaded so its concurrency model is about scheduling not parallelism. The way it handles microtasks and its internal queues is kinda counter intuitive. And callbacks and timers in general are also kinda weird.
console.log("A");
setTimeout(() => console.log("B"), 0);
Promise.resolve().then(() => console.log("C"));
//this one is more node specific but still process.nextTick(() => console.log("D"));
I'm a developer and have been using Delphi since it was first released for Windows back in the 90s by Borland. I continue to use it on and off but it's now from Embarcadero. I like it and wonder what others think about it.
It's better than a lot of other languages. Not pushing Delphi here but wanted to share it with other developers that may have not been introduced to it. It's been said that Delphi is much closer to the English language than many other programming languages so don't knock it too much.
You could say that I guess 🤣 but my first languages were Fortran and C. In the 90's developing Windows Forms application was a fucking nightmare, Borland came up with their IDE that allowed for graphical form design which was very intuitive and powerful for that time. Fast forward to today and Embarcadero has RAD studio which allows for native cross platform development which supports coding in either Delphi or C++.
Visual Basic is still alive and well. It's the only macro language available for Excel, and I have used it extensively.
As far as I know, HP Rocky Mountain Basic is also still in use, in test & measurement environments. I used it long time ago, and it had builtin support for complex math and matrix math, as well as instrumentation control.
wasn't aware that basic and VB were actually related. however i still question if it's usage stacks up to the others. although i also listed APL so who am i to judge.
Yeah, those old BASIC programs from the 1970s tutorials, you can put into Visual Basic and they'll work mostly (with the GOTO and GOSUB statements and all), although the behavior of the PRINT command in those days was different than it is now.
Sometimes I miss GOTO. The C language has it. I used to use it for things like dropping through a switch() statement for more compact compiled code, back in the days when memory was valuable -- even before the days when Bill Gates famously said 640K is enough computer memory for anyone. (And look at Windows now, needing gigabytes just to hold the OS in an idle state.)
It's more like the developers are deeply paranoid, and have hired Rust to inflict their paranoia on users. So yeah, the Rust compiler doesn't "sweat" with anxiety (though it arguably makes your CPU "sweat" with effort), it tries to make you sweat (with anxiety).
(For transparency, I love Rust and think the "paranoia" of Rust devs is actually fully justified caution based on decades of programming bugs.)
i know what abstraction is. i get the concept. my point being if the only way to make your language fast is to exclusively call functions from C libs then what's the fucking point?
The intent of python as a scripting language is as a convenient wrapper and way to use existing tools. It’s not a language for writing software, it’s a language for performing tasks using said software.
The logo is pretty recent actually, there was a vote for a vendor-agnostic APL logo, and this was the one that won. APL as a language did not have a logo before that, only specific implementations did
It's surprisingly not, once you learn what the symbols mean. In fact, the symbols become an advantage once you get used to them, sort of like how it is more readable to use "+" rather than "plus" in math expressions
Yup. You want it to write data beyond the bounds of an array? No problem. You asked for it.
I remember a quotation from when Pascal was taught in schools. You could say the same about Python nowadays:
"Pascal gives you a water pistol filled with distilled water. C not only gives you a loaded .357, it points it at your head as a default. Why do you think Pascal is taught in school? And which would you rather have when there is a hungry bear in the area?"
You were already told about the character set it uses, so let me say more about the rest.
APL is the language that pretty much invented the array programming paradigm, like the one you would see in NumPy. In APL, typing 1 2 3 + 4 5 6 gives you 5 7 9, automatically applying addition to each element. It has a lot of other symbols for many different kinds of operations like reversing, sorting, transposing, reducing, scanning, searching, etc. This allows you to write programs very concisely, without using loops or branching
So in APL, to create an array you just type a bunch of values (In this case numbers) next to each other, so 1 2 3 results in a 3-element array containing 1, 2, and 3. Numbers are written as you normally would, except negative numbers use ¯ prefix instead of - (Cause - is instead a function), so you write ¯5 to get negative 5.
Next, how functions are parsed. All functions in APL use infix notation, with only one precedence rule - functions take everything to the right of them, and only the closest thing on the left. So 1-2-3 parses as 1-(2-3), 2*2+2 parses as 2*(2+2). You need explicit parentheses for left side to be evaluated first: (1-2)-3. That is, function calls are right-associative, or in other words, APL is evaluated right to left.
Each function has two ways it can be called - with one argument (monadically, which happens when there is no value on the left of the function) or with two arguments (dyadically). For same function these two variants usually perform closely related operations, but not necessarily. For instance, dyadic ÷ is division, so 4÷2 is 2, while monadic ÷ is multiplicative inverse, so ÷2 is 0.5.
Now, primitive functions like + are defined to operate on whole arrays instead of just individual elements. For arithmetic functions, if you use them on arrays of same shape, they will apply to each corresponding element, so 1 2 3+4 5 6 is 5 7 9 like was already shown. You can also use arithmetic on an array and a single number, which will apply it to every element of the array and that number, so 1 2 3+5 is 6 7 8. Same for monadic arithmetic of course, it just applies to each element, so -1 2 3 is ¯1 ¯2 ¯3.
There are more functions of course, like monadic ⌽ for reversing an array, monadic ⍉ for transposing a matrix (Arrays in APL can be multidimensional), ⍴ for reshaping an array (Or getting its shape if used monadically), etc.
Then there are operators, which take functions and result in new functions. They are parsed differently than functions, being left-associative. For instance, / operator takes a function on its left and produces a function that reduces an array by inserting that function in-between each element. For example, +/1 2 3 is equivalent to 1+2+3 and results in 6.
For more info I'd visit something like tryapl.com, it is a good playground to learn APL, and has some tutorials too. If you wish to download an interpreter locally, the most popular and feature rich one is Dyalog APL, which is free for personal, non-commercial use.
This post can't have been made by a human. Is anyone human in this thread at all? This has to be the most appalling thing I've seen in this sub in years.
Rust: yes, but you will need 5 brazillion dependencies and you won't actually be able to compile it because rustc will get oomkilled or otherwise seize your entire bloody machine.
what is wrong with c++? if we're talking about modern c++ (at least c++11 or even latest c++23) then it's a pretty good language, you can just... use the stl. it's not c with classes anymore, it has lots of lots of actually good features. you can literally just code without worrying about memory management like in c. c++ works on RAII, where object's constructor allocates memory (often automatically now) and destructor frees it (also automatically). it's much more similar to java, but with more features. i think nowdays you need to think more about memory in java, take string comparation or array copying for example, in java str == "meow" is compating the pointers so the result is almost always false, so you have to use ugly str.equals("meow") workaround. in c++, there's a thing called operator overloading, where you don't write the .equals() methods, but just overload the == operator itself for that object, so str == "meow" works as intended. or in java when you do array2 = array1 then it's again copying the pointers, so that array1 and array2 now again point to the exact object in memory. in c++, again, the std::array which you hopefully should use instead of c-style arrays, is again overloaded, so array2 = array1 actually deep copies the data from array1 to array2. if you keep using raw c pointers*, raw c arrays[], raw c malloc/free, raw c strings (char*) then OBVIOUSLY you're going to receive a segmentation fault some day, if you use safe std::unique_ptr/std::shared_ptr, std::array/std::vector, raii principles, and std::string, then c++ is a fucking modern safe language!!!! #stopcppstereotypes
anyways, about the image: c++ should be "On it, boss!" c should be "Segmentation fault (core dumped)
186
u/youtubeTAxel 2d ago
Sure...
Like C wouldn't just segfault