« first day (465 days earlier)      last day (1311 days later) » 

00:42
it was supposed to have more stuff
but uh
we never got aroudn to it TM
 
5 hours later…
05:43
!!/run kh
@lyxal Hello World
!!/info
06:26
@user15966645 Welcome to the Vyxal chat room!
 
5 hours later…
11:05
!!/goodnight
@Ausername o/
I mean, no one uses functions :p
in The Nineteenth Byte, 3 mins ago, by A username
Do you guys think Vyxal silently erroring during parsing counts as erroring?
This'll probably be something we fix during the rewrite
Well-formed code is much easier to parse than various nonsense like this.
But I more mean error reporting
Currently errors are not that helpful
11:16
Also we should keep some errors, they're good to have for various things.
I'm not saying getting rid of errors
I'm saying report them better
Actually tell the user something went wrong
Like it ain't our fault if people do something obviously wrong
Errors currently don't give out enough information really
I think I've discovered your favourite boolean value
11:23
Oh no!
Cursed language feature: True, False and Maybe
11:49
dah wrong chat
@lyxal Why tell me something went wrong?
(but +1 to better errors)
@user because you're a sussy baka
@lyxal for the beta access, do you have to make an account first (before the application)
@math no
The account comes once you're approved
ah
11:54
@lyxal no ur mom
Gottem
Wow so original and creative
That’s because my name is Original
Damn, my phone just suggested my real name when I started typing “my name is”
@lyxal how did you animate the stickman?
Mobile app
and didn't the music get copyright claimed?
there are no ads
11:59
I think I'm that small of a channel that no one cares
And besides, I couldn't even monitise if I wanted to
You need way more subs
100 I think
Oh, and the lyxroll is also unlisted
So no one is going to be looking for it any time soon
12:14
!!/run `Iz bork agan?`
[@AaronMiller: 58715271]
STDERR:
[POST /execute] returned 500
That's a yes
@lyxal WOW I tried a gpt-3 alternative and it's great!
!!/run `⌐⇩ in λλ Ṫɾ, »ẋ ⟇»'s ÷₌ λ⋎ «ɽ on it`
@lyxal jump in the Cadillac, girl let's put some miles on it
12:20
@math very accurate
@math I just said Vyxal's a great code golfing language, it's easy to understand and
Why is there a table?
@lyxal uh me?
> When you're at the bottom of the table
> When you're at the bottom of the table
dang, ninja'd
12:24
lol
uh what?
bottom line of your generated text
wait a sec
I lost it already...
it's generating something else
Where is it getting all the names from?
@AaronMiller yes, I saw, but I already generated something else and i put a 1000 character limit
12:31
ah
@lyxal Can I try a social experiment now?
sure
I'm thinking of questions
ugh
have you read harry potter?
wait end experiment
END
I see that gpt-3 is more powerfull...
who's loax?
> It’s been a while since I’ve played a video game. I haven’t played a single game with a gamer since my childhood, so I”m really not sure I‘d be able to play it anymore. I“m glad I―d be playing a video gamer, because I�​m not so sure it‚s gonna be the real thing.”
Why did it use 5 different characters for the contractions, including an unprintable?
12:39
@AaronMiller where?
> I've I”m I“m I―d I�​m it‚s
Actually six; it used both directions of double quotes
@lyxal can I try an experiment as well?
@AaronMiller sure
I totally didn't get distracted by watching the Muffet fight from undertake because of the recent spider dance reference in the Lost Chapter in JSAB
@lyxal What's your favorite color?
#beedab
@lyxal Apparently gpt-neo thinks your favorite color can only be expressed in code:
It'd be great if the JSFiddle led to that code, but it just 404's
@lyxal Ooh, I like that. That's a very good green.
> Vyxal, a brand of organic cotton is a great source of fiber to produce organic cotton. So, you can use your own cotton for your own purposes, as long as you follow the cotton manufacturer's instructions and don't have any cotton to grow.
12:52
Okay so methinks I should probably start discussing how we gonna handle flags with the rewrite
because flags relying on global variables made the clean up not yes
so the question is, how do flag changed variables get to their intended place?
I suppose the first step is to classify the flags based on where they actually impact program execution
Instead of global variables, we should have it create a separate folder in the filesystem for the flags, and have each flag in a .txt document, so the interpreter can read the contents of the folder to see what the flags are. /s
btw, the current flags are HjLsMmṀvcfadrSCOoKlGgWṠRDṪṡJV
@AaronMiller I considered this, and that could work online, but offline doesn't use sessions
The first category of flags would be "end of execution" flags
these are jLsdṡJlGgWSC
the second category of flags is "before execution" flags
@lyxal Why do it with the sessions, when we can just make everyone share the same flags?
these are HfachṠ (the before execution flags)
@AaronMiller flag communism
the third (and probably final) category would be "throughout execution" flags
<Insert popular communism meme here>
12:58
the first two categories of flags are easy to handle
they just take place before and after execing the source
but the third category is where the main pain will happen
So why is using global variables no?
because multiple files
and we tried that
but it didn't work
obviously it didn't
because otherwise we wouldn't be having this whole rewrite in the first place ;p
Consider for example the M flag
it makes number->range generation start at 0 instead of 1
multiple functions use vy_range
such as all the functional programming stuff
oh hey hyper
I'm just presenting the issue of handling flags within the code
nothing to do with mod flags
Why don't we make a separate file that takes in the flags, then edits all the other files to hardcode the changes made by the flags, then edit them back at the end of execution?
13:06
that sounds messy though
Nah, it's fine. Just don't look at it too closely. /s
another idea is to pass a flag context to each function call
as in, it would store whether each flag is called
it would be constant, meaning it wouldn't be modified
that reminds me
I need to quickly add something to the code style guide
brb
@AaronMiller That sounds cursed
@user I'm pretty much just making jokes because I have no clue how to implement the flags in a better way. I'm more just here as a sounding board for y'all's ideas.
Oh lol
13:10
@user Wait, that could be modified slightly to be perfect for my new language! :thonk:
Piggybacking off that idea, one way we could implement flags is by making the user fork Vyxal and edit the code /s
Lyxal pushed a commit to Vyxal/Fresh-Beginnings: No direct stack stuff
Good idea
@user I like the sound of the implicit decorators you mentioned
@user For the online interpreter, there could be a separate site for each possible permutation of flags, each of which is linked to a different fork of Vyxal.
13:13
@lyxal Yeah, they could make calling stuff a lot less verbose
@AaronMiller nevermind that's what I'd do if Redwolf ever got his way and got flags counted as bytes again
like seriously tho
If we use those, though, it may be a good idea to make the context parameter the last parameter (and probably also a default value)
@user correct
@lyxal Easier solution: Finish our chicken business :P
@user would you be able to describe those decorators within the documents/specs/ folder?
13:15
Sure, let me look at the package first and try to understand it
@AaronMiller easier: just have a lazily generated dropdown of each permutation. People choose which permutation they want
and I'm not even \sing here
Oh come on, you wouldn't do that
That's a lotta permutations!
@user thank you. It doesn't have to be an extremely comprehensive description - just enough to give everyone a reasonable idea
@user yes I actually would
ಠ_ಠ
13:16
if flags were counted as bytes, I'd move to a whole bunch of flag permutations and claim different versions
This is something I've often considered as a back-up plan
"Here is my answer in VyxalOH, which is entirely different from VyxaloH" :P
because this is assuming enough people would upvote a meta proposal to make flags count as bytes
because hopefully we'd all vote against it, and enough people would see that the current site consensus suffices
We could always brigade such a meta proposal (and I don't think it would have that much support anyway)
Ninja'd
@lyxal Why not just add more flags and just go full metaVyxal, with each version of metaVyxal representing a dfferent permutation of code and flags?
@AaronMiller because flags are supposed to supplement actual programs. metaVyxal suggests that flags just solve the challenge in 1 byte
flags are only meant to be byte savers, not program eliminators (unless you're doing something really trivial)
13:21
@lyxal s/suffices/allows Vyxal's exploitation of site consensus to make it superior to all other languages
@AaronMiller even then, it doesn't
codegolf.stackexchange.com/a/231796/78850 with flags gets it down to only 16
to win, one would need to beat 05AB1E's 14
Hold my beer.
(For legal reasons that's a joke)
ysthakur pushed a commit to Vyxal/ysthakur-patch-1: Add implicits to the code guide
PR #198 (Vyxal/Vyxal) opened by ysthakur from Vyxal:ysthakur-patch-1 into Vyxal:Fresh-Beginnings: Add implicits to the code guide
I know we said no commits straight to main, but that's for code
documentation (or at least new docs) should be fine imo
PR #198 (Vyxal/Vyxal) was merged by Lyxal from Vyxal:ysthakur-patch-1 into Vyxal:Fresh-Beginnings: Add implicits to the code guide
Lyxal pushed a commit to Vyxal/Fresh-Beginnings: Add implicits to the code guide (#198)
13:28
in The Nineteenth Byte, Jul 10 at 5:12, by Redwolf Programs
No, because I trust you wouldn't actually do something as extreme as that
Redwolf underestimates my determination
anyhow
it's time for sleeping to happen
*Changes documentation*
*Site crashes*
@math okay, so I'm gonna wait for my gpt-3 application
@math Same
@math it picked up on the small bit of french in why.md and ran with it
@math I now know both you and Aaron are at least 18
13:32
@lyxal really?
french where?
oh there detre
I already extened why.md with gpt-3 anyway
@lyxal yes, that's why I chose it to see how good gpt-neo really is
> Put simply, Vyxal exists because golfers need a golfing language - and because golfing languages could be better.
3 mins ago, by lyxal
anyhow
3 mins ago, by lyxal
it's time for sleeping to happen
that's all gpt-3?
@math "Put simply, Vyxal exists because golfers need a golfing language - and because golfing languages could be better." is
I really am going to sleep now
13:34
wow
no creating fires while I'm gone
!!/'night
@lyxal o/
@lyxal Too late
lol
At last a decent fire image
There, now the starboard is on fire.
13:42
nice
@lyxal How?
@user There's a box you have to check on the gpt-3 application saying that you're 18.
Remember, everyone's 18 on the internet.
Ah
 
1 hour later…
15:09
ysthakur deleted branch Vyxal/ysthakur-patch-1
 
2 hours later…
16:59
That moment when you realize that you've been using Vyxal long enough to have memorized the SCCs for "Fizz", "Buzz", and "Vyxal"
ha, nerd
haha lol *cries*
@AaronMiller ༼ つ ◕o◕ ༽つ
@VyxalBot ༼ つ ◕o◕ ༽つ
@VyxalBot You always know how to cheer a guy up when he's being bullied by subatomic particles. :)
2
17:40
@VyxalBot How did that happen?
Ah
gonna be honest with you
i forgot i could do that
and actually logged in to the vyxal bot account manually
@hyper-neutrino Good, what's your password?
17:44
What's your email?
Provided that this is allowed, I'd be able to tie with jelly flagless, but there is a bug that prevents me from doing so. That bug could be fixed simply by adding vy_ to a single line. :(
kekw
Once HN answers, we will have access to a mod's account mwahaha
ooh, useful!
Oh, the 11 we can commit!
17:48
Delete every single answer that doesn't use Vyxal, Scala, or StackExchange
*tries it*
*it works*
@hyper-neutrino Not a valid email >:|
sorry my finger slipped
17:52
thx
@user His email is on his website, remember?
nice!!!!!!! prepare to be haxxed hn
 
3 hours later…
20:44
!!/run `y chat ded?`
@AaronMiller y chat ded?
20:57
!!/run `bcoz der nutin 2 tawk a bawt`
@user bcoz der nutin 2 tawk a bawt
 
2 hours later…
22:39
@hyper-neutrino do you think we now have enough information planned to start writing the parser?
23:12
Because I think that if we do, progress on writing the parser should start
23:36
I think so too

« first day (465 days earlier)      last day (1311 days later) »