#development
1 messages Β· Page 246 of 1
"Oh yeah, I need to use C in my project, I'm gonna create a package just for that"
generally yes it makes your project less cluttered
Mentally ill behaviors
plx
Which one of you is the original
gm
me when my source code is 500mb of pure text because all my dependencies use verbose langs and are all embedded
idk I put my on at like 2020
relatively late
machine code is the most verbose out of all of these
LMAO
you compile a program, even with dynamic linking, and it becomes way larger than the source code
so JS would be smaller
You have to compile a program to run it
You started arguing about the dependencies being embedded in rust
and unwieldly repo managements
you don't have 500 mb of source code on js
i was actually targeting rust there
not js
lol
I mean it's the same in both case
you don't have 500 mb of source code on rust either
you're probably thinking of compiling

^
Yes
have you seen a rust codebase
no more than the average swift full tree of code
when compiling you easily end up at 2GB project file
way more
swift codebases are tiny
the entire swift compiler
swift 6
is like
3gb
including
llvm
and all its dependencies
lol
the entire compiler
mfs after pulling the 200000000 packages needed
rust code is about as concise as swift
π
and that's to say not very
thats crazy
Actually very if you look at it from a different perspective
Both very expressive languages
bro what
You use a small amount of code to mean a lot compared to like C or something
i am so confused
does anyone here actually code in swift properly
like
more than
here or there
this is so false
π
it's at best a tie between rust and swift if you want to die on this hill
swift's literal language guidelines are "omit needless words"
have you ever seen rust code
yes
i dont consider that concise though
That's the primary complaint about rust
no, because :
- toolchain is garbage
- no(/poor) unsafe
- ABI is dogshit
- SwiftUI slop etc
- static binaries
swift is very safe
swift is safer than objective c
objectively
all this work for it to not even be perfectly safe smh my head
it is literally one of it's core features
if you can't use it to make safe code
that is like
I'm talking about unsafe support
a full on skill issue
?
oh that makes more sense
i mean
that makes more sense that what you just said
yeah
that makes more sense
because swift is safe as fuck
that's my point
rust is safe but you can also unsafe to do things
.pointee .makeCallable
you can also do unowned self
I call that garbage unsafe support
Look at ellekit code, you'll understand what I mean
swift's ownership model is bloat
reference counting is for chumps
Oh yeah that too
i mean if you primarily use low level c based langs then i get not liking swift
gm @harsh junco
wait wtf ellekit is written in swift? Literally the worst decision one can make
it's more abstract and does a lot more for you and takes a lot of that control away
gm!!
its so funny how personally you take any criticism of swift
It is
not personally
No you're literally taking them personally
they are not objectively wrong things though
maybe you think they are, but for most of these not objectively so
like me with rust in 2020
idk if rootfs was therr
pretty much everything ive said has been more or less correct bar a few things
Never used rust nor swift much
just because you say correct things doesn't mean we only say incorrect things
I'm keeping myself sane
Become a systems developer with C
Objc users go to hell
also why is the toolchain garbage
what is wrong with the toolchain
π
all of us are just asserting things that are somewhat subjective and impossible to "prove" objectively either way
You need to watch the video by tsoding daily on swift
all 3 of us
ive built that shit from scratch hundreds of times atp and all i can say is its slow on old hardware
but other than that
idk
@lime pivot back me up please
fr
What does that have to do with anything?
you said the toolchain is garbage and i have pretty intimate relations with the toolchain
love/hate relationship
(metaphor obviously don't twist)
seems like he likes the lang?
also
idk why
but he's using incorrect syntax
i think
i thought they removed support for the ;
Before you go haywire, the video came out a few years ago
it's not swift 6, prob swift 5.10
fr
; was never official syntax
not even from swift 1.0
it was just there to help objc users move over
like a lot of old syntax was
swift has so much syntax bloat
fr
swift methods are far more concise than their objc counterparts
mfs when they have to decide whether to use guard if or if let
Ive heard that consistently from people that actually use swift a lot
there's a whole bunch of redundant features and that makes it annoying to read and learn
You do rust, you shouldn't be allowed to talk on that matter
It doesn't really have the same issue
rust is borderline not readable by a non rust dev
if let unwraps the optional conditionally if it can be assigned guard let unwraps and if it cant, it throws
I'm talking about the syntax redundancy
I mean yeah at least rust has a point on the syntax
Rust doesn't really have a bunch of random garbage features that all do the same thing
everything that's different does something different
else {throw whatever}
same thing
I forgot the example I got from mai in swift
its not the same thing else isnt a proper error throw
It feels like they kinda just wing it when developing swift
"ermmm actually throw isn't a proper error throwing"
Just make functional code
fr
Haskell is worse don't word it like that
@slim bramble do you know if flexing works on apps written in swift?
oh good luck
?)
UILabel *label = [[UILabel alloc] initWithFrame:CGRectMake(0, 0, 200, 50)];
label.text = @"Hello, world!";
label.textColor = [UIColor redColor];
[self.view addSubview:label];
let label = UILabel(frame: CGRect(x: 0, y: 0, width: 200, height: 50))
label.text = "Hello, world!"
label.textColor = .red
view.addSubview(label)
UIButton *button = [UIButton buttonWithType:UIButtonTypeSystem];
[button setTitle:@"Tap Me" forState:UIControlStateNormal];
[button addTarget:self action:@selector(buttonTapped:) forControlEvents:UIControlEventTouchUpInside];
[self.view addSubview:button];
- (void)buttonTapped:(UIButton *)sender {
NSLog(@"Button tapped!");
}
let button = UIButton(type: .system)
button.setTitle("Tap Me", for: .normal)
button.addTarget(self, action: #selector(buttonTapped), for: .touchUpInside)
view.addSubview(button)
@objc func buttonTapped(_ sender: UIButton) {
print("Button tapped!")
}
You might wanna go to the first floor, be far far away from sharp objects
and so on
me when swift is far more concise
across the board
objc repeats the name of types over and over and over and over
Yeah and the fact you have to use interop makes it garbage
having to specify function parameter names in function calls:
because UIKit isn't made to be used with swift, you're supposed to be using ShitUI. But ShitUI is absolute garbage
But that's wrong
you dont have ot use interop
idk what you're talking about
you can remove @objc
and itll work
lol
but yes
you are right
uikit is built for objc
Yeah but it's still going to be using interop under the hood
because swift still have to dispatch messages
swiftui was built for swift
and dispatching messages in swift is insanely slow
and it serves its purpose as a declarative language excellently for most people
obviously you can dislike swiftui
swiftui was built for swift
it also sucks
HMMMMM
No it doesn't
skrilll issue
SwiftUI consumers when tasked with making their ui render a stable 60 hz without "optimizing" it
Yet, Apple themselves still uses objc(++) for the most of iOS environmentβ¦.
they dont use objc for ui
Because you aren't running any serious app
i am
Well performance issues are a common thing I've seen
what are you talking about
what apps
are you running
that are more "serious"
in swiftui
That isn't quite true, they are rewriting some frameworks to swift
Idk how you could not see this unless you don't talk to anyone here
swiftui has issues sometimes for sure
but its not like oh use swiftui immediately 10 second overhead
Some app designed for consummers
thats complete horseshit
thats bad app design
not bad swiftui
i can get the same thing to happen on uikit
with poor code
easily
in fact
i already have
7 calayers in
and i have that already
10 second overhead when starting the app up
for my dc client
7 fucking calayers
7
It seems apparently it is a bit difficult to have good app design on swift ui
its really easy
most people manage it quit ewell
however
its very easy to get lazy
with swiftui
and not optimise
and thats where you ahev issues
its not as easy to do that
with uikit
uikit is more rigid
requires you to put in more effort and generally means more optimised ui
why do you have to focus so hard on optimizing swiftui when it doesn't seem to be a big issue on other frameworks
:/
you dont
swiftui lets you feel lazy
so
when you do have to optimise
it feels like more effort
you dont get that on uikit to boot
so it feels the same
Idk I don't really believe it. Some of my friends I know aren't the lazy kind
its not lazy as a person
swiftui lets you stop thinking critically
because it's so easy to write
which leads you down bad practicies
it is one of its flaws
swiftui should be more rigid
i deeply dislike that about it
swiftui is not without its faults
Lazy programmer kind
but swiftui just being "oh you use it and its like so slow and so poorly made and shitui"
it just isn't
like point blank it isn't, it was swiftui 13
it just isn't anymore
if you put the same effort you put into uikit
into swiftui
you'll get the same result
i'm going to be brutally honest
damn backtracking into a specific version cutoff
swiftui 13 was 1.0
so yes
it was poor
Making progress
uikit 1.0 was poor
swiftui has had time to mature
swiftui started off shit
i will give you that
the 10 view limit
was shit
but it is no longer shit
Swift compiler telling you "couldnβt computer whatever"
what?
Nope
but not utterly slow
couldn't compute the complexity of something I thought
Yes
Or the type
no
I know what you're talking about
use what you wanna use 
The compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions
yes
that is shit
I remember what superbro was always complaining about
there's no one tool for the job. sometimes one is objectively (ha) better, sometimes one is just more comfortable for you
completely agree
lol
SwiftUI on iOS 13 genuinely was bad
it's not react native
you didn't really say that
tes
you basically said all of them were programmer faults
you always change what you're saying repeatedly
??????
Lame, moving 16Player to havoc
I don't think you did until you started backtracking at the end
even React Native is pretty damn good. like to be clear the only thing web about it is that the program logic is js
I feel like definitely the central argument that was conveyed was that
even if you put a weasel statement at the start
I don't really remember
Discord is pretty garbage if you ask me
But any time someone brings up a legitimate fault you brush it off and deny it as incorrect
swiftui is no worse than uikit in my opinion
if the only example you're aware of is Discord then I'd say it's doing great
what?
most faults
that were brought up
read yourself
were user rror
there were a few
that were not
if your code is taking 10 seconds to startup
99% of the time that is your fault
at what point is it 'everyone is using it wrong' vs 'it is designed wrong so the user is using it wrong'
Because thatβs the only app using react native I use
that you know of
No, that I use
doesnt instagram use it?
Itβs not afair
and like
It wasn't even brought up, you brought this up on your own and debunked it separately to try and reinforce your argument
all meta apps
they use bits of it around the app
I think that's called something but I don't remember
!??!?!?!?!?!?!?!?!?!
Facebook does dogfood React/React Native
you're the one that came up with an app taking 10 seconds to start
I DIDNT BRING IT UP
I did
π
Because thatβs shitui
@slim bramble fuck you
Gm Amy
gm
I forgot where I was going
I brought it up like 100 messages earlier tho
you ruined it
If he does just bring it up now, Iβd say it ainβt my fault
you put it in his mind
planted the seed of relevance
yes
ngl i feel like if your app takes 10 seconds to start it's not language error
swift is perfectly competent
like
i get not liking it
I said cold start
It does take 10s
ill submit to thinking its bad
then that's not swift's fault
sometimes an engineer must accept that the tool being used wrong by people is an indicator of the tool being designed wrong
Never had this issue
it takes effort to make an app take more than 2 secs to start
On objc
^^^^
you've never one to one compared a swift app with an objc app
With 10s Iβm obviously exaggerating but itβs very very slow
it's especially a problem when you keep loading an app up with 3rd party deps, especially if they late load things or do other funky things early on
in all my testing which has been very extensive when porting swift to ios 6 which may i remind you runs on a fucking 3gs, swift is no slower than objc
the language itself
is not slower
I don't even know how it could be
it's still just⦠machine code. being produced by LLVM
Yes because it canβt do otherwise
SWIFT IS LITERALLY OBJC IT CANNOT BE SLOWER
THIS TOO
IT MAKES OBJC CALLS
THE CALLS ARE THE SAME THE RUNTIME IS THE SAME
if anything, the objc runtime is the slow part
YES
LMAO
π
OBJC IS LITERALLY THE CORE RUNTIME OF SWIFT
SWIFT RELIES ON IT FOR ALL ITS LOW LEVEL FUNCTIONS
do we need to shout
You didnβt read my message earlier so Iβll say it again, but every time you make an objc call from swift, the data types have to be converted, same thing happens afterwards. So Iβd say swift issue
MY CAPS LOCK BUTTON IS FORCE ON oh wait i can use shift
that happens compile time
not runtime
π oh my god
what types are we talking about here
@lime pivot I think you missed a large part of what I was saying earlier
Idk what the hell is going on now
I didn't read anything before I was tagged into this
because if it's calling into objc, an int is alwys an Int32, NSInteger is Int, etc. those are 1:1
β
they're compile time lmao
What's that mean
They are not
strings get converted to ns strings at compile time
You canβt convert a type at compile time
a swift String might need to be converted to UTF-16 for NSString but it's possible it looks ahead and knows it has to init the string that way
utf16 π₯
but absolutely a string coming back from NSString to String is backed by a utf-16 view
i mean thats true
it's not really converted, string is nsstring
I don't know the rules for when it becomes something else, or what that something else even is. might be utf-8? idk
actually no
string is swift
string is stdlib
string isnt converted at all
string is a native type
idek what you're talking about
Me when String.convertToNSString() whatever
Because it doesnβt need to always be called
However Iβd argue that for iOS 6, itβs going to be called a lot
utf-16 gets used because it's way easier to build logic around. utf-8 mostly serves to get rid of null bytes so it's more efficient in being transferred around the internet etc
I'd argue it's called about the same amount on iOS 26 as well if using UIKit
yeah oksy
so uh
string is not backed by ns string
at all
maybe some apis
need ns string
but swift string
as a language feature
is not converted
at all
read the source
it isnt
plus AFAIK utf16 can't represent all of the Unicode space
you can convert strings to ns strings
but the string type
does not rely on anything
It can't because you can literally put an infinite amount of data inside an emoji
no
no
but no encoding can fit every emoji in a single code point either
ZWJs and such
not only that but swift implements the entire unicode standard standalone in the swift stdlib
so no conversions there either
emojipedia has been hot garbage since it got sold
well anyway yes, it's 4 bytes utf-8, f0 9f 98 80
Because there's data inside
π₯
unsafe stuff for you asw
d83d de00 in utf-16
found the conversions to ns string
its purely for interop
never called when pure strings are used
so it's still 2 16-bit ints
internal func _isEqual(_ other: AnyObject?) -> Int8 {
guard let other = other else {
return 0
}
if self === other {
return 1
}
// Handle the case where both strings were bridged from Swift.
// We can't use String.== because it doesn't match NSString semantics.
let knownOther = _KnownCocoaString(other)
switch knownOther {
case .storage:
return _nativeIsEqual(
_unsafeUncheckedDowncast(other, to: __StringStorage.self))
case .shared:
return _nativeIsEqual(
_unsafeUncheckedDowncast(other, to: __SharedStringStorage.self))
#if !(arch(i386) || arch(arm))
case .tagged:
fallthrough
#endif
case .cocoa:
// We're allowed to crash, but for compatibility reasons NSCFString allows
// non-strings here.
if _isNSString(other) != 1 {
return 0
}
// At this point we've proven that it is an NSString of some sort, but not
// one of ours.
defer { _fixLifetime(other) }
let otherUTF16Length = _stdlib_binary_CFStringGetLength(other)
// CFString will only give us ASCII bytes here, but that's fine.
// We already handled non-ASCII UTF8 strings earlier since they're Swift.
if let otherStart = _cocoaUTF8Pointer(other) {
//We know that otherUTF16Length is also its byte count at this point
if count != otherUTF16Length {
return 0
}
return (start == otherStart ||
(memcmp(start, otherStart, count) == 0)) ? 1 : 0
}
if UTF16Length != otherUTF16Length {
return 0
}
/*
The abstract implementation of -isEqualToString: falls back to -compare:
immediately, so when we run out of fast options to try, do the same.
We can likely be more clever here if need be
*/
return _cocoaStringCompare(self, other) == 0 ? 1 : 0
}
}
#endif //_runtime(_ObjC)
}```
I know, but swift still isn't quite fully integrated into the os
also I just discovered this, neat site https://unicode.link/
that's a valid criticism
they're working towards it though
they will get there
but it isn't there right now and that's fair enough
I don't think it can really happen without compromising either storage or one language
Swift uptake at Apple was very slow
the horrors of swift currently running on the Secure Enclave Processor
Don't think it will
but utf8 can represent anything given enough bytes
they didn't want to touch it till ABI stability
yep
They're gonna keep it c
thank god
yeah it will
yeah c
why would they do SEP in swift
that'd be dumb
c is the right tool for the job there
without a doubt
no like some of the SEP modules right now are embedded swift
you can extract them from recent fw
what?
You literally cannot fit swift sep in the sep chip
yeah
wtf ?
feel free to explore
They got to SEP π
Are you being fr tho ?
ngl i don't like the idea of swift in sep
SEP does NOT do unsafe
SEP is low level
all low level code is unsafe in one way or another
still mostly in C https://blog.timac.org/2023/1019-state-of-swift-and-swiftui-ios17/
controlled unsafety
(swift fatal error)
In iOS 16, only 4 apps used the SwiftUI-based app lifecycle. In iOS 17, this figure has grown to 14 apps:
goddamn
they really took a long ass time
swiftui did get really good in ios 17 tho
to be fair
math users when the function is continuous on R
because pre iOS 16 SwiftUI is dogshit
math users when the function is NOT continuous on R
errr
average unsafe user
how many days until doomsday
how many days until
Is 1436 too much
you don't notice
You have to figure out where!
lol
1513
that's the fun part
mute point
damn thats less than i thought
the point at where I mute this channel
.
Coincidently, that's also when iOS major updates started getting slower and slower
You're absolutely right!
You're absolutely right!
You're absolutely right!
ngl
It was funny
i have to give you that
They wanted to relive the funny
Is 18 latest
26
iOS 17 is better than iOS 18 which is better than 26
Is 26 after 18
i dont think so tho
ios 18 is better than 17
ios 17 is hot garbage
ios 17 took 3 minor updates to get stable
Ngl thereβs like no public motivation to even find kexploits anymore
Apples security is kind of insane
Especially on iPhone 15+
I mean I'm on an iPhone 12
only have to deal with SPTM and pac
which is basically done
since there's enough vulns released
iOS 17.4.1 pov
iOS 17.4.1 got like an INSANE amount of SPTM/PPL bugs fixed
Sure but thereβs no kernel exploit
Thatβs what we actually need
And there are none
Itβs been 3 major versions
A first for iOS
@wooden yarrow how do you handle profile pictures in dsc
Do you have some kind of universal cache?
SDWebImageManager handles
Oh
Iβll just use Data URLSession and UIImage then
I nedd to make my ui propagate faster
βOnlyβ
Never
π

If 17.4 got krw then maybe things would change but idek of a patched PAC bypass for 17.4
there probably will be a PAC less bypass in the 20 that released
Wait if youβre on an iPhone 12 you have PPL to deal with
But as Iβve said before, PAC is the hardest part 
Isn't it SPTM
Ah I miss the good old days where you didnβt need to bypass 8 layers of security to jailbreak your device
pac bypass? just tell it to get out the way
Real as fuck
Ngl just do that to everything
Tell iboot to take a holiday
It needs to take itβs off days
Itβs overworked
Needs a break

the interesting statistic would be users opinion on stability to overlay this
cause uhh, stability and battery life have only been getting worse over the past fwe years
Thatβs true
Hereβs the thing though
I really doubt itβs swift
Like if Iβm beinf brutally honest
For all swifts faults
I think itβs just sloppy work
Iβve noticed general bugs since like iOS 16 becoming common place
And most of the actual OS itself is still objective c
And not only that, the number of objective c binaries has increased nearly as much as swift
The overall os has jus gotten so much more bloated on the whole
im not saying its a swift problem, i mean specifically swiftui
usability is in how well the user interface performs
Ngl I think Apple has done some poor things with their SwiftUI apps
Then again I feel yhe same about their UIKit ones
The settings app is so broken
You guys wonβt experience it on modern devices but on the se 2 you really feel how many corners apple cut
i really dont know whose fault it is though
I have a very deep seated suspicion that itβs sloppy code
i fear a lot of the engineering effort is being placed into the AI shit and the core OS is being left behind f
Totally agree
And I donβt get it
Apple will never be an ai company
Ever
They know that
Apple fundamentally does not work as an ai company
Their core relationships with their customs and shareholders is not constructed like that of an ai company
So idk what theyβre doing tbh
Just integrate ChatGPT
Let them handle ai
Theyβre still making big bucks
Itβs not that bad
Although foundation models is super nice
im kinda all for the ternus takeover of apple
he seems like the kind of guy who would put the core products first
Who is that
senior vp of hardware engineering
I barely watch keynotes past 2019
hes the one who is most likely to take over Tim
Well
Tbh
If he didnβt take core products seriously
I feel there is a real problem
ππ
he's the guy who has been leading the apple silicon macs
Which are fire yet shit
Grrr
whats ur main gripes with them?
storage I would agree, memory I can see why their against it
Memory is purely because they charge a scam
well no not really
They are running a Disney villain type scam
i mean, not really? it allows them to get a much higher bandwidth
Itβs so over priced
memory is tied very closely to the soc
Yes
No
.
A15+
My main gripe is price
this is why they're incredibly efficient on gpu/ai
better memory bandwidth and better thermal performance
the main bottleneck for igpus is memory bandwidth
Either make it replaceable or charge actual prices for it
Because they are laughing their way to the bank with their pricing right now
They charge so much that it isnβt even funny
Itβs a downright robbery
Storage is worse
storage is a bit of a piss take
They charge a 100% surcharge on almost all options for storage
AND itβs soldered
Storage should be m.2
It just should
it kinda already is on the desktops
Fire profile picture btw i just no tied
Noticed*
Itβs apples way of saying βfuck youβ
its just laptops where its not replacable anymore
π€¨
Also on desktops Apple would have been raked over the coals by enterprise if they hadnβt done something
No company is sinking that much into a machine that could become deadweight with no backup plan
(No good manager is anyways)
I certainly wouldnβt for my team
unfrotunately everyone on the team doesn't care
the only people who care are the people buying the machines
the developers just want the insanely powerful hardware
Yep
and the IT teams will pay for it
Yep
Itβs a shit house system
I hate corporate buying policies
I cannot tell you how deeply I hate them
My MacBook Pro m4 pro still hasnβt shipped
Iβm so pissed off
Ahhh but what about m5
All I saw from Apple was βai ai ai aiβ
I mean Iβm not lying
Like bro I do not give a shit about ai on a 14 inch laptop are you for real
because I can
I guess so
Fair enough to be honest
why wouldn't i
unfortuinately my laptop has to actually be portable
16 inch is portable
The 15 inch I have rn is a bit small
Ngl
I mained 14 inch for so long
And then j switched to big laptops
Cannot go back
never said you were
For development theyβre so nice
I thought SPTM was A12+, but I'm apparently mistaken
Big screen to see all my code have a simulator on the side
my laptop is so scratched up I kinda love the aesthetic
The only thing I like about MacBooks is the hardware bar storage
Damn they make good hardware
They really nail it
Apple haters when their shitty laptop is made out of plastic
I mean thatβs not entirely fair
My X1 Carbon is fantastic
But Apple makes good feeling and looking laptops yes
They charge 1.5 times what they should for them
But they are good
Nop
A12 doesnβt even have the hardware support
I kinda love my t480
A13 idk, A14 does
but its just not got the horsepower I need anymore
True
Theyβre a bit on the weaker side
Especially the gpu
yup
π
ha i have the nvidia gpu
That gpu has haunted me for years
So I just need to exploit PPL and kernel
and its still pretty grim
Aw man
nvidia mx150
idk felt like pinging you
π¬
Grim indeed
Yeah no doubt about it apple makes good mobile
Chipsets
Idk I feel like the idea kinda falls apart on desktop
Desktop for me is something where j donβt care about sound or size
I need raw power and I need control
And PC serves well there
Apple used to give you that
Even the 2019 Mac Pro is good enough ish
Got pinged by Rootfs cuz he felt like it, time to spam 16Player.deb cuz I feel like it
Jk, I love his little French ass
Pause that sounds gay, he is just a really good friend
Digging the holeβ¦
DO IT
I tried 16Player
fr
When I was using iPhone SE 1
Nah
Oh
It was crap on the se 1
@slim bramble tap in leans modpack server
I can't
Wasnβt optimised for it at all
yeah
Why
we donc have a SE1 to test
Iβm sure itβs fine on other devices
Simulator?
Test some bitches bruh
peep eotj
The size or performance?
We not keeping ts private bruh
Thankfully I didnβt buy that
Yeah I did but I regretted it not because itβs a bad twsak idk if it is or not
Itβs just clearly not made for iPhone SE 1
who gaf
mmhz
this is why u pirate tweaks
even if ur not gonna keep it pirated and buy it
its good to test
i lied actually it was webassembly https://pixelomer.github.io/Shijima-Web (edit: so apparently this doesn't work in discord's in-app webview or in safari's private browsing but otherwise it works i swear)
i've decided that excessive r/jailbreak exposure is unhealthy, so instead i now microdose r/jailbreak on saturdays

Yeah
Nah
no
π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π
BOO!
ooh i'm so scared etc
get a job loser you are worse than that other stinky ass cat @shrewd smelt
Fr
Youβre genius on rjb
Therefore worse
Valid
Also valid
@kind herald @lofty juniper Hey your so called genius is being off topic
how did you ping me with this reply :/
why is discord pinging me for blocked messages 
Just letting you all know I have blocked people on Discord. I want to ensure you all know I have blocked people because it is important. I am so irritated at select people that I have blocked them, I hope you know that. Did I mention I have blocked people on this server? I wonder what they're saying, I'll never know. Cuz y'know, I blocked them.
The js func`srrinf` syntax in js is a special thing where it resolves all the variables passed to it, then splits the string and passes the variables seperatlt to the function. This means the function can handle assembling the string and as such is able to prevent sqlite injection

