Readit NewsAround 2010, I did experiment with things like Silverlight and SVGs. SVGs was OK, but the performance quality was not there. It might be a lot better now.
It assumes you want a single malloc of Vec3. It tries to behave as if you are doing a 'new' in an OOP language.
Let the programmer decide the size of it.
Mock example (not tested)
struct Vec3* Vec3_new(size_t size)
{
if(size <= 0) {
// todo: handle properly
return NULL;
}
struct Vec3 *v = malloc(sizeof(struct Vec3) * size);
size_t i;
for(i = 0; i < size; i++) {
v[i].x = 0.0F;
v[i].y = 0.0F;
v[i].z = 0.0F;
}
return v;
}But it can be hard to encourage adoption. It’s not HTTP, or a conventional queue system.
Requires lots of explanations, thinking, and eventually meetings.
However -- I cannot praise the use of ROUTER-DEALER !! What a GREAT pattern for sending large chunks of data without waiting for a reply for each.
HTTP is not fit for such a task.
However - I totally get you! Trying to explain certain decisions really does take up time and effort. Before you know it, I have lost 4 hours one day, a few another, etc.
In the end you ask if I should have done something mediocre... but everyone understands.
("mediocre" is not the correct word to use. I mean I could have gone with Kafka or RabbitMQ. It's just an extra layer which would have involved infrastructure and further delays (at that time))
Whether it's a program that does something well... or simply a function/procedure --- it all depends on the problem I/we are trying to solve.
I never liked using the word "Microservices" but my aim has always to build SIMPLE solutions. I learn new words in this world. For the most part I am building "Miniservices" but there are a few that are considered "Microservices" but again are not complicated!
I just like to refer it as "Distributed Computing" because the solution can be anywhere between Monolithic or Microservices. Truth is you are building a combination of them that communicate in one form or another.
I will always remember a Till system (past job) that was sending data to the server poorly and slowly with a Monolithic solution and a Database. Was it becoming a pain to handle with new shops being added in Europe? Yes. However, this is NOT the fault of Monolithic. It's just the solution that was used for "good" originally but is struggling now.
The solution I replaced it with allowed data being sent to the server using ZeroMQ. It worked out well.. was fast and reliable. Each section was broken down on the server. Again - is it is perfect solution or does it prove that "Monolithic is worse that Micrsoservices" (or Distributed Computing) -- NO! Truth is our software is a mix of them all!
There has been different terms and meaning to it - but we all know the "OOP" thrown about since the mid-to-late 90s is the Java way.
A typical Java book back then would have 900 pages.. half of which is explaining OOP. While not focusing fully on Java, it does help transition that knowledge over to Delphi or C++ or.. eventually.. C#, etc.
Overall -- we all knew what "Must have good OOP skills" means on a job advert! Nobody was confused thinking "Oh.. I wonder which OOP they mean?"
I have a love/hate relationship with OOP. If I have to use a language that is OOP by default then I use it reasonably. While the built in classes will have theor own inheritence -- I tend to follow a basic rule of no higher that 2. Most of the time it is from an interface. I prefer composition over inheritence.
In C#, I use static classes a fair bit. In this case, classes are helpful to organise my methods. However, I could do this at a namespace level if I could just create simple functions -- not wrapped inside a class.
OOP has its place. I prefer to break down my work with interfaces. Being able to use to correct implementation is better than if/switch statements all over the place. However, this can be achieved in non OOP languages as well.
I guess my point is that OOP was shoved heavily back in the day. It was shutup and follow the crowd. It still has it's place in certain scenarios - like GUI interfaces.
This site sucks. Why does it use php, and why is every link a query? Just make it a static page.
condolenses to her family and closest friends.
I'm really enjoying Linux. It's one of those things that makes me somewhat passionate about computing for the first time in a long time.
As a Linux user since 2006/7, I totally understand. I had atleast 1 computer at home that would dual-boot to either Windows or Linux. Regardless, I had to have a Windows system.
My reasons may not be the same as yourself - but I do still get stuck and HAVE to use Windows from time-to-time. It's not just for playing games or work related. It's sometimes a simple file I have to download, fill in and email back. The file is likely a Microsoft Excel or Word file and while OpenOffice/LibreOffice is good most of the time, there is bound to be something off.
Sometimes my kids will have homework (going back a few years now) and it would only work on Internet Explorer despite the fact Chrome was dominant back then.
(I remember, back in 2008, I would ensure the websites I created had decent support for Firefox as well as Internet Explorer, despite my boss telling me "everyone uses Internet Explorer" - that soon changed by 2010 with Chrome)
Thing is these problems are not the fault of Linux, or the Office suite, or the web browsers. The problem was the people using files specific to a brand, or focusing on specific web browser, etc. However, many people wont view it like that. In these scenarios.. Linux was the problem.
I always remember writing my Resumes for recruitment agencies. I would hand over it is 3 formats. ODT, PDF, and DOCX. I did this because I was not sure how the DOCX version would look on Microsoft Word. Of course, it looked great in Open/Libre Office.
I always encouraged the PDF version.
> I'm really enjoying Linux. It's one of those things that makes me somewhat passionate about computing for the first time in a long time.
100%!
I tried various Linux flavours. Starting with Ubuntu. From memory, I tried Mint, Fedora, Slackware, Manjaro, etc. I cannot remember when I last tried a Distro. It likely ended by 2010. Since I have just stuck with Debain.. for both client and server installs.
I said goodbye to Windows a few weeks ago.. fully. While Windows has served my purpose in certain ways, I have always been critical of Microsoft and their practices. I would agree that Windows 11 is a solid OS.. its the "features" added on top that slows it down.
This time, I have the latest version of Debian. No dual-boots.. nothing else! Despite being aware of Steam's Linux support for some time, now.. I actually gave it a shot and suprised how easy it was. I then tried Heoric (Epic) Launcher and just as easy!
It probably helped that my laptop is an AMD. I normally hear effort and difficulty with nVidia but I did not have much trouble 10 odd years ago. Not sure what its like to properly work today.
So far I have tried 4 games. 2 modern games, and two 90's games. All of the worked! Whiles the 90's games had their issues at times.. this mostly refers to using a gamepad.
The 2 new games (sure this is not a good experiment for all games) have worked flawlessly!
Honestly.. in my opinion.. installing Debian appears exactly the same as it was back in 2010.. maybe more. I rarely had issues. It's just this time I am able to play Steam and Epic games and installing dotnet is easy on Linux.
Let's not forget the work Steam are doing. We have a new Steam Machine. While being marketed as a new games console it's still a PC... and new users will try it out. For the younger generation, it might increase the Linux skills and spread wider adoption.
The only thing Linux has against it is time. Time is something humans lack... we lack patience! I knew that one day Linux would get better games support. It was possible even back in 2008. I managed to get GTA3:ViceCity working through Wine.
Mark my words. Linux will gain marketshare. The only part I am concerned about is infiltration of corporations jumping all in. It's not the kernel I am concerned about as it's protected by the GPL.. it's the larger corporations selling their products which the average user adopts and eventually becomes "required" software in most distributions.
The best way to understand this is, in an alternate universe, Microsoft drops Windows and encourages everyone to use Linux. How do you think they would get involved. Just think about that.
I still remember gasping when I first saw the basically unattainable (for me) Japanese‑import N64 running Mario 64.
Such an interesting and varied gaming landscape back then; for example, the Wipeout experience on PSX was beyond the N64 port in that particular niche, for its own set of reasons.
In typical fanboyism, I viewed the main SGI systems are the superior systems to the N64.. but they were for the office.. not the home. The other was Panasonic M2.
Of course.. either the N64 was released in the UK or not far away, I remember walking into PC World (a cool computer shop at the time) with a demo of Tomb Raider. I believe it was running a Voodoo1 card and the realisation kicked in. The N64 is already surpassed.
Wasn't long before we had a Voodoo2 card and the first game we played was a demo of Turok:Dinosaur Hunter. It was much better than the N64 version (which I owned)
Once I started playing GLQuake it was a PC master race.
It was at this point I snapped out being a Nintendo 'fanboy' and accept that hardware gets you so far... its the games that make a console.
I still think the N64 was a great console. Goldeneye, Ocarina of Time, etc. Great memories. Also got a Gamecube, Wii, and Switch.
As I got older and snapped out of the fanboyism, I realised the Playstation was a good console. I am on the fence with the Cartridge vs CD argument. There are cases for both. If we look at Mario 64, many aspects worked well on Cartridge. I guess faster load times and transition of music. With CD.. you have CD quality music and more variation of textures and level design (generally speaking)
Putting all the aside, Playstation is just as much capable of doing a good Super Mario 64 port despite the (many like) PS1 jaggy polygons.