• monkyyy (30/30) Jul 28 * 1000 messages in a thread this week
• aberba (2/3) Jul 31 I thought you were ai but now I have proof you do feel pain. 😂😂
• monkyyy (4/5) Jul 31 Ai's generate grammatically correct sentences without insight; I
• Kapendev (6/14) Jul 31 I'm not a fan of function coloring, but there are some instances
• IchorDev (4/5) Aug 12 @live doesn’t colour anything because it doesn’t affect which

monkyyy <crazymonkyyy gmail.com> writes:

* 1000 messages in a thread this week

* the cia pushing rust several months ago(making the news every 
day since)

*  live

* 2 decades of debating about the d's gc

* arguably nan init

Allot of time and attention has been going towards an unsolvable 
and irreverent problem. With imaginary nonsense solutions like 
rusts bower checker promising it will fix everything.

There *cant* be a complete solution, if you could decide where a 
pointer could point with 100% accuracy why not decide the halting 
problem? While there trivial partial solutions like... *drum 
roll* slices, note slices are data structure and not "code 
coloring" and deal with indexing.

If you want safer code, *provide nice to use data structures* 
that provide clever, *partial* solutions on opIndex. Not  safe vs 
unsafe vs  live vs whatever code coloring hell.

I *do not care* and will never lift a finger to use safe code, 
and if you quickly survey what people *do* and not *say*, we are 
no where near mathematical perfect safety, instead my passwords 
are trivial to find online, people rarely care about strong 
password, users are a weak point, and credit card numbers end up 
as plain text by fortune 500 companies paying thru the nose for 
fake security.

99.999% of physical locks are trivial to pick, and your life is 
harder to back up and arguably more important then your data; yet 
society functions and moves on. Why is that, if I "need" a 16 
character password and 3 factors of authentication to protect my 
10$ on paypal?

Please dont spend any more time on code coloring.

aberba <karabutaworld gmail.com> writes:

On Sunday, 28 July 2024 at 19:54:44 UTC, monkyyy wrote:
 * 2 decades of debating about the d's gc

I thought you were ai but now I have proof you do feel pain. 😂😂

monkyyy <crazymonkyyy gmail.com> writes:

On Wednesday, 31 July 2024 at 20:15:53 UTC, aberba wrote:
 I thought you were ai

Ai's generate grammatically correct sentences without insight; I 
produce grammatically incorrect sentences which are deeply 
insightful. I don't understand the confusion.

Kapendev <alexandroskapretsos gmail.com> writes:

On Sunday, 28 July 2024 at 19:54:44 UTC, monkyyy wrote:
 There *cant* be a complete solution, if you could decide where 
 a pointer could point with 100% accuracy why not decide the 
 halting problem? While there trivial partial solutions like... 
 *drum roll* slices, note slices are data structure and not 
 "code coloring" and deal with indexing.

 If you want safer code, *provide nice to use data structures* 
 that provide clever, *partial* solutions on opIndex. Not  safe 
 vs unsafe vs  live vs whatever code coloring hell.


I'm not a fan of function coloring, but there are some instances 
where it's OK I think. For example, when dealing with safe and 
trusted code, function coloring can help to identify a potential 
issue. But yeah, good data structures are always better than 
function coloring or bower checker stuff.

IchorDev <zxinsworld gmail.com> writes:

On Sunday, 28 July 2024 at 19:54:44 UTC, monkyyy wrote:
 Not  safe vs unsafe vs  live vs whatever code coloring hell.

 live doesn’t colour anything because it doesn’t affect which 
functions you can call, which has been argued is one of its 
shortcomings.