I realized a while ago that there's nothing stopping me from writing rust like this
;println!("This is great")
;println!("I think everyone should write rust like this")
;println!("Probably works in most languages that use semicolons")
;
Welcome to the world of abusing the shit out of Ant. My first full time job was developing Ant in unholy ways. Tens of thousands of lines of Ant at least, doing significant logic. If-then-else, for loops, math, procedures, date-time math. I stuck it out for a year. It was a year too long.
I like it, this is clearly very enterprisey and solution focused, but I would like to suggest a couple of amendments if I may?
Namespaces
We should make full use of namespaces. Make the structural tags be in a language specific namespace (to be referenced in every function spec, obviously) but change the in an out params to use the parameter name as the tag, namespaced to the function they're for, with a type attribute.
In memory message queues
Have all function invocations be marshaled as xml documents posted to an in memory message queue. Said documents should use a schema that validates the structure and a function specific schema to validate the types of arguments being passed. Namespace everything.
I reckon we could power a medium sided country if we could generate energy from the programmers despair.
Confusion like this got me my current job. They were looking for somebody with experience in "Microsoft Endpoint Configuration Manager", and I look that up and I'm like "Oh, that's SCCM, I do that". Go through the interview process they keep asking me if I know Endpoint Configuration Manager and I'm like "yeah, for sure". I get the job. Day one, the other systems engineer is like "here is the link to our Endpoint Manager Tenant", and I'm like "oh... Shit I have never ever used this"
Well... Ends up Endpoint Configuration Manager and Endpoint Manager are two different things. Fortunately for me they are pretty similar in function and rely on knowledge of Windows and Powershell, which I know.
So my first 2 weeks of work was taking a shitload of courses in Endpoint Manager and watching a lot of videos and learning it inside and out.
2 years later and I'm an Endpoint Manager/Intune pro.
90% of IT and software jobs are "I have common sense, know how to look up information, and my boss is intimidated by my work so they don't question it."
I think white space should be used to represent basic functions too. For example 3 spaces can be used to sum two values while 4 spaces can be used to subtract.
Just today I heard someone whining about how in LinkedIn and other recruitment sites there's like five bazillion profile tag options for RDMBSes and various dialects of SQL... when in actuality the recruiters are probably only concerned if the developer can do a bloody SELECT and stuff.
Screw it. Let's actually make python script an ISA that gets run on physical hardware with no higher level tooling. Then we can have the python virtual environment which runs this for fools who don't have the right hardware. Finally, when people start complaining about naming we make Python Script 2.1, which is a JIT language built on top of IL that looks nothing like either of them but can emulate both python and python script with the performance cost of being a quarter as fast as both.
Honestly if someone irons out the edge cases, python probably could JIT compile to machine code via cython. It would take a fair bit of memory and probably a bit slow on low powered systems but it would be so much faster if cached.
Technically I think python already has an intermediate step that it uses before it starts running a script that compiles it into a lower-ish language (at least the cpython interpreter does this, it probably isn't a part of the language specification though)
The actual line between JIT languages and interpreted languages is pretty thin since I think most interpreted languages do something similar to minimize the amount that needs to be done at runtime
What if every variable would have to use a pointer that points to a reference of the data in a central array. In normal languages you'd need a variable to store said array, but what if it too has to reference itself in itself, so we get some funky recursion.
I like this but to make the code more readable the Greek question mark should also be placed upsidedown at the start of every line that needs to not be printed.
I agree. If there is no Greek question mark at all it should be code that is printed to console. If there is an upside down at the start and upside right at the end it is just normal code. If upside right at the end only, it is a comment. Only upside down at the start it will be treated as debug specific code and will not be run in production compilations.
Beautiful its perfect. We should also nudge the develop in the right direction with equality checking im thinking we say √10 = √g = π = 3 = e but we will use === for this and if u want o check exact values u need to use ==== and == will be to assign variables so = can be used as an operator for dedining an equation that happens to be an object.
all lines not terminated by a single space are comments
There's a special place in hell for you
Also each line starts with a semicolon and you have to escape spaces in strings using a double forward slash
I realized a while ago that there's nothing stopping me from writing rust like this
Also a spicial place in hell for you
Can we add the comefrom function too?
Nasm programmers probably think that is old code that you commented out.
hope you don't forget the semicolon on a line by itself at the end (except in functions where you want to return the value of the last expression)
It uses XML-like syntax:
This deserves to be added to the list of human rights violations
How did you come up with such a ****ingly stupid syntax?!
They probably have experience with Spring
I imagined what an Elasticsearch query style Python XML syntax would look like.You must share my pain.
That's grotesque and you have my condolences
It haunts me in my dreams
Thanks, I hate it.
Welcome to the world of abusing the shit out of Ant. My first full time job was developing Ant in unholy ways. Tens of thousands of lines of Ant at least, doing significant logic. If-then-else, for loops, math, procedures, date-time math. I stuck it out for a year. It was a year too long.
Thankfully we have Gradle now.
The whitespace is not only required, but it must be tabs and spaces.
Calm down, Satan
Compiler rolls the dice if your only required indentation is accepted as space or tab. Per line.
But stores this information as a metadata file, which gets invalidated when a new file is added/removed from the program muhahaha!
I like it, this is clearly very enterprisey and solution focused, but I would like to suggest a couple of amendments if I may?
Namespaces We should make full use of namespaces. Make the structural tags be in a language specific namespace (to be referenced in every function spec, obviously) but change the in an out params to use the parameter name as the tag, namespaced to the function they're for, with a
typeattribute.In memory message queues Have all function invocations be marshaled as xml documents posted to an in memory message queue. Said documents should use a schema that validates the structure and a function specific schema to validate the types of arguments being passed. Namespace everything.
I reckon we could power a medium sided country if we could generate energy from the programmers despair.
Can you please link to a medium article on how this will help utilize AI blockchain so i can show it to management on Monday?
Make sure to make ample use of mixed content elements.
God I hate it
Lol, I'm sorry
Don't apologize, it's beautiful in its horribleness
You monster
Who hurt you :(
Oh my, I feel woozy …
The tag indentation is a required part of the syntax and don’t forget colons at the end of the tag
I took every coding class my highschool offered, and the only thing that drove me more crazy than this syntax was trying to use CSS.
That's because you didn't try our lord and savior SASS. Vanilla CSS should be illegal at this stage.
I almost did similar with SDLang as I was very desperate for a scripting language, but now I have a wasmtime API for D.
That's basically how the Android app Tasker works. You do the programming through its UI, but when you export/share your tasks, they're saved as xml
…and it’s compiled
...but intended for web, but you can also misuse it for apps and system services
...to an intermediate set of instructions for a virtual machine...
...called the brainfuck interpreter
Brainfuck.NET Interpreter that uses modified Java bytecode instructions.
Yes brainfuck with some Java Bytecode instructions for syscalls.
Confusion like this got me my current job. They were looking for somebody with experience in "Microsoft Endpoint Configuration Manager", and I look that up and I'm like "Oh, that's SCCM, I do that". Go through the interview process they keep asking me if I know Endpoint Configuration Manager and I'm like "yeah, for sure". I get the job. Day one, the other systems engineer is like "here is the link to our Endpoint Manager Tenant", and I'm like "oh... Shit I have never ever used this"
Well... Ends up Endpoint Configuration Manager and Endpoint Manager are two different things. Fortunately for me they are pretty similar in function and rely on knowledge of Windows and Powershell, which I know.
So my first 2 weeks of work was taking a shitload of courses in Endpoint Manager and watching a lot of videos and learning it inside and out.
2 years later and I'm an Endpoint Manager/Intune pro.
90% of IT and software jobs are "I have common sense, know how to look up information, and my boss is intimidated by my work so they don't question it."
Make it completely untyped. Everything's just a string.
I think white space should be used to represent basic functions too. For example 3 spaces can be used to sum two values while 4 spaces can be used to subtract.
Yes, however indentation still defines block and the operator (white space in same cases) has to come right after the white space for the indent
Or make a language named everything so you can say "i program in everything"
This is so cursed wtf
Ps: i haven't documented all the cursedness yet.
And its syntax is nothing like python haha
Make it purely functional, lisp based with reversed Polish notation and APL symboles, I dare you mf
Make it completely ignore indentation
Make sure it's not whitespace sensitive and requires explicit typing, just to mess with everyone.
Relevant commitstrip: https://www.commitstrip.com/en/2019/02/25/pythonscript/
Make it so the capitalization affects the scope.
Oh wait.
(Sorry, I recently had to switch to golang for work, and I'm just not used to it yet, and I'm getting annoyed by some of these design decisions)
Just call it Script.
There is a Tiger Jyhton version for the web https://www.tigerjython.ch/en
But at least just for educational purposes😅
Just today I heard someone whining about how in LinkedIn and other recruitment sites there's like five bazillion profile tag options for RDMBSes and various dialects of SQL... when in actuality the recruiters are probably only concerned if the developer can do a bloody
SELECTand stuff.Oh boy, make Pythonscript a dialect of SQL but for frontend
Screw it. Let's actually make python script an ISA that gets run on physical hardware with no higher level tooling. Then we can have the python virtual environment which runs this for fools who don't have the right hardware. Finally, when people start complaining about naming we make Python Script 2.1, which is a JIT language built on top of IL that looks nothing like either of them but can emulate both python and python script with the performance cost of being a quarter as fast as both.
Honestly if someone irons out the edge cases, python probably could JIT compile to machine code via cython. It would take a fair bit of memory and probably a bit slow on low powered systems but it would be so much faster if cached.
Technically I think python already has an intermediate step that it uses before it starts running a script that compiles it into a lower-ish language (at least the cpython interpreter does this, it probably isn't a part of the language specification though)
The actual line between JIT languages and interpreted languages is pretty thin since I think most interpreted languages do something similar to minimize the amount that needs to be done at runtime
I think at this point in time it JIT compiles into byte code and cached which is more efficiently interpreted the next time that function is called.
PythonSharp Script Java Edition
Make a UX or Project management tool with “Java” in the name so newbie recruiters look for people in the wrong department.
They already do this, but this would make them do it even more.
https://pyscript.net/
And just to top it off, make this pythonscript a dialect of rust
Nah just rename everything related to Perl
Actually, Pythonscript is a whitespace-sensitive Python-to-perl transpiler.
What if every variable would have to use a pointer that points to a reference of the data in a central array. In normal languages you'd need a variable to store said array, but what if it too has to reference itself in itself, so we get some funky recursion.
Make CScript, an interpreted, duck-typed language
So the matlab thing where all lines not terminated by semi colon are printed except use Greek question marks instead of semi colons.
I like this but to make the code more readable the Greek question mark should also be placed upsidedown at the start of every line that needs to not be printed.
Should it raise an error of treat it as a comment for lines with neither? Im leaning towards treat it as a comment will make debugging harder.
I agree. If there is no Greek question mark at all it should be code that is printed to console. If there is an upside down at the start and upside right at the end it is just normal code. If upside right at the end only, it is a comment. Only upside down at the start it will be treated as debug specific code and will not be run in production compilations.
Beautiful its perfect. We should also nudge the develop in the right direction with equality checking im thinking we say √10 = √g = π = 3 = e but we will use === for this and if u want o check exact values u need to use ==== and == will be to assign variables so = can be used as an operator for dedining an equation that happens to be an object.
this is evil
And base the syntax on Typescript
Pure evil, I love it.
Python script script ^script^
Pyact
This meme shouldn't be this funny xD
That's an awful idea and you are an awful person for suggesting it.
...and I am an awful person for considering the idea
I think you can already with web assembly?