@CoreFusionX I can think of some vectors for improvement. Ultimately though, IDC... I just have fun with my kernel :)

@NoToJavascript

well, there are some optimizations you can make. for example:
- Remove text mode
- Specialize the kernel functions/interrupts for webbrowsers to use
- build drivers around web usage

Keep in mind that this is just a fun project to do some OSDEV and hopefully bring a small community together ;)

telegram @BinaryByter

my time to shine!

@Linux Hehehehe yup, its meeeee 😁

@theabbie I'm proud now, Sorry

@theabbie This is the first push notif I got from devrant in a year, what did I do to deserve this?

@terminal434 Honestly, enums should be implemented as aliases for ints

I use exclusively krita. its f-ing good

@bvs23bkv33 Huh? what?

@linuxxx Thanks! I wish you, and everybody else who reqds this all the best! I hope that i might get into programming again eventually

@dontPanic Yea!

Linux is a hobbyists system. what do you expect?

@RememberMe What. Those were done because of consumer demand, because people wanted to be able to do increasing amounts of stuff with their computers

lol some can do quite similar graphics on just a CPU with delays because they have too many frames xD

No.

Linux is a horribly flawed hobbyist system. Ive experienced enough fucked up shit - like an ext 2 fs not boundhecking meaning that you could wipe you entire server by filling a file

C++ is a very bad programming language, promoting inefficient programming. Its exception system is horrendously low, its standard library contains so many utilities that force you to code inefficiently. To top it off, modern cpp compilers suck arse....

IMHO both of those inventions mark the time perios where devs started becoming lazy, thus creating the need for terrabyte hdds, gigaherz processors and gpus

C was made initially as a portable language that could easily be ported. Dont think that it was made to do everyrhing

Linux was initially a Minix clone, not meant to be used anywhere. Yes, it has so many minix desigb decisiosn that are bad for perf that its hilarious to watch people who think that linux is cool

you wont get below O(n*m) with two checks unless you start using heuristics. Look into boyer moore

@spacem Java applets were a plague

@irene they arent, imd umb

@Fast-Nop i meant 32b, sorry 😅

@Fast-Nop i'm too lazy to go back to the code - but int is compiled to 64bit on clang on my machine on my os

@Fast-Nop qword now.

@Fast-Nop btw: i got it to compile with -03 without overoptimization. I also noticed, that my asm code did copy by DWORD, so I changed that too.

Now we are looking at a result of

19s vs 1.9s

@Fast-Nop the type int should change the size of the r/w since by definition, pointer arithmetic is different on int* than on void*

@Fast-Nop idiomatic C++ won't make stuff that much better

since I use the variable type int, it should do a dword by dword copy.

malloc and new do virtually the same thing (in some implementations, new will even call malloc, so that just adds overhead) so shrug. Making me create a std::array <a, size> won't really make stuff better, since I still have the same buffer to copy

@C0D4 please... i'm trying to forget

@irene i don't see how you would copy a chunk of memory in bulk without iterating

@jotamontecino and here I am questioning the output of my C++ compiler... I think that we have very different definitions of lightweight ;-)

@irene yes, thats why it works with std::copy. I dont see the difference to buffers, though

@ganjaman Some people think that its as fast as it gets ;-)

*not going to mention any names*

@irene since copy is templated, it can take pointers - which are pointers to buffers