Welcome, Guest. Please login or register.

Author Topic: One unified OS for the future?  (Read 35937 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Fats

  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 672
    • Show only replies by Fats
Re: One unified OS for the future?
« Reply #89 on: November 17, 2014, 09:43:40 PM »
Quote from: danwood;777695
If you ran a Workbench replacement like Dopus Magellan, chances are you'll prefer Ambient, if you used Workbench with some add-ons, you'll feel more at home on OS4.  Of course, you can run Dopus Magellan on either system as well.

Just down to taste really.


Exactly, I was always a workbench + VincED + Dirwork user and I prefer OS4 Workbench over MOS Ambient. That's also why I think an unbiased comparison is impossible.
From the other side I do think MOS has some better technical lower level implementations compared to OS4 so as the latters use of .so objects.
Trust me...                                              I know what I\'m doing
 

Offline Paulie85

  • Full Member
  • ***
  • Join Date: Dec 2009
  • Posts: 146
  • Country: 00
    • Show only replies by Paulie85
Re: One unified OS for the future?
« Reply #90 on: November 17, 2014, 10:34:41 PM »
Quote from: Blinx123;777698
Just an idea but if people wanted to create a unified Amiga OS, perhaps it would be wise to start with something like NetBSD and lay out an Amiga esque userland on top of it.

That way, we'd have a kernel that could run on anything from 68k to x86_64. And at least for non-68k systems, running 68k applications wouldn't make much of a difference (they require emulation anyways).


I always thought it would be great if MOS team worked with OS4 devs using Aeros as a base for OS5. It could bring together the best bits if all three OS's with the power, drivers etc of Linux. It would be multiplatform as well.
 

Offline LiveForIt

Re: One unified OS for the future?
« Reply #91 on: November 17, 2014, 10:56:29 PM »
Quote from: Fats;777725
From the other side I do think MOS has some better technical lower level implementations compared to OS4 so as the latters use of .so objects.

So how is not supporting .so object better then supporting .so objects?

100% of all AmigaOS librarys are not .so files.

The only .so files you find is the onces ported from Linux. And having .so file support most defiantly helps poring over software like QT, hey if you don't like software that is ported from Linux your free to stick to only MUI and Reaction software, but chances are that even they contain linux libs ".a" files that have been linked into it.

Take mplayer for example do you know way mplayer exe file is so big?  
Way is Odyssey Exe file so big?
Is statically linked .a files more or less amiga then sheard objects .so files?

Well its always a good idea to study, have you read the Hyperion blog about this.

http://blog.hyperion-entertainment.biz/?p=481

What you should find out is that OS4 Kickstart does not use sheard objects, because its not available until the OS is loaded, shared objects are not "shared" in memory, you should also notice the advice against making shard objects and when creating library for AmigaOS.

So way do we have shard object support? Well because statistic linked .a files make your programs fat, and also exe files that are statistic linked like mplayer for example has every thing built in, so if you wont to replace FFPEG lib in mplayer, you can't but if FFPEG was a .so file or .library file that be possible, so way are not all Linux libs ported as Amiga libraries, well because its a lot of work, and so that never happens.

Simply put "shard object" support is a compromise.
« Last Edit: November 17, 2014, 11:25:58 PM by LiveForIt »
 

Offline amigadaveTopic starter

  • Lifetime Member
  • Hero Member
  • *****
  • Join Date: Jul 2004
  • Posts: 3836
    • Show only replies by amigadave
    • http://www.EfficientByDesign.org
Re: One unified OS for the future?
« Reply #92 on: November 18, 2014, 12:18:42 AM »
Quote from: Fats;777725
Exactly, I was always a workbench + VincED + Dirwork user and I prefer OS4 Workbench over MOS Ambient. That's also why I think an unbiased comparison is impossible.
From the other side I do think MOS has some better technical lower level implementations compared to OS4 so as the latters use of .so objects.

@Fats,  Ambient in MorphOS3.7 can be set up to look like and function almost exactly like Workbench of any version, and vice versa.  AmigaOS4.x's Workbench can be set up to look like, and work more like Ambient.  Neither would be 100% the same as the environment they were trying to copy, but this argument alone should never be the sole reason for choosing one OS above the other to use as their preferred platform.  When I see this statement used for the reason a user chooses one platform instead of the other, it makes me cringe and think that these users have not researched either choice very well, or even tried to customize either OS setup, which used to be one of the first things that most Amiga users did to their own systems.  Where has that old Amiga trait of customizing and tweaking the user interface to their liking gone, or have most of us just become too lazy to do that kind of customization these days?  I think that most Amiga users are smarter than that and should use other comparisons of features, performance and available hardware to run the OS on, as better reasons why to choose one OS instead of the other.  The "Look and Feel" justification is one of the easiest differences to point to though, so it is often mentioned.  I just hope it is not really true that users are making their choice on the "Look & Feel" factor, when it can be adjusted so easily on either OS to "Look and Feel" any way they like, even almost exactly like the other OS they are turning away from by making that decision.  I prefer to read that a user has chosen one OS or the other for reasons of cost, or new vs used hardware, or free  and Open Source vs commercial and Closed Source.  At least those reasons make more sense to me, but not because of the "Look and Feel" of the user interface when it can be so easily changed.  This little rant about the "Look & Feel" of either OS is not meant just for you and I am not assuming that you made your choices for that reason, but I have seen other users who have made specific statements like that before and your mention of "Look & Feel" just reminded me.


It is refreshing to see some reasonable discussion about the differences between AmigaOS4.x, MorphOS3.x, AROS (don't know what version range it is currently at these days) and AmigaOS3.x (emulated or native).  Spirantho and I just had a great and rather lengthy discussion about the same topic (differences) via email, where he suggested we copy and paste our pages of discussion into a forum thread as an example of how to express different opinions, without becoming hostile or fighting with each other.  His and my opinions are similar in a few areas, but it was apparent that we had many different opinions and experiences.  His preference is to use and support AmigaOS4.x, while my preference is clearly MorphOS3.x, though I support all flavors of the Amiga/Amiga-Like experiences.

His perception of the pros & cons of each were very different than my own and I learned some new things about both platforms from the things he wrote.  He also reinforced some of my perceptions on some of the more technical aspects of both, as his knowledge and expertise in coding and understanding the under lying structures of the OS itself exceed my current understanding.

(Edited out part of our private communication that should not have been paraphrased by me, out of context)

Some of the most interesting discussion I had with Spirantho (Ian Gledhill) was his perspective on the amount of low level infrastructure work that the Hyperion developers have been focusing on, to allow AmigaOS4.x to move forward to the goals of being able to implement the Protected Memory and SMP features promised for AmigaOS4.2.  Since the MorphOS Dev. Team members have openly stated that those two features are not possible without breaking the legacy support for Amiga 68k software (or at least without undesirable consequences, due to the number or nature of compromises that would need to occur to allow such features to be added to MorphOS, or any platform which has an AmigaOS 68k software compatibility built-in)[/SIZE],

Since the MorphOS Dev. Team members apparently don't think those features are feasible without unwanted side effects, they probably are not doing any work to add Memory Protection and SMP to MorphOS, and instead their plan is to wait until they are forced to make an architecture switch, at which time they will abandon Amiga 68k legacy support, or "Sand-Box" such legacy support and use UAE to provide it, or some similar path forward.

I won't debate which path is better or worse, because I don't think such an argument can be won or lost, but there is no denying that the path that Hyperion programmers have chosen has  taken (and will continue to take) hundreds, if not thousands of programming man-hours to work on implementing these features into AmigaOS4.x, without sacrificing too much of their own legacy support.  We won't know how successful they will be, until AmigaOS4.2, or what ever version number they decide to use for the release version that includes these long awaited features, is finished and available for purchase and testing.

Memory Protection & SMP support are two features that would be very nice to have for lots of obvious reasons, but I am not sure that they are "Make or Break" features for me, with regard to my decision to continue supporting the development of AmigaOS4.x and using my X1000.

I got along very well for years on AmigaOS3.x and MorphOS without those features, so as long as I can still get some newer and more modern software applications (and a few new games) to enjoy on my X1000 running AmigaOS4.x, I probably will never complain if full Memory Protection and SMP support does not work, or never gets finished.  If/When they do get finished, for me, that will be a big bonus, as it should increase the speed a few applications will be able to run at, will allow some applications to work, that currently can't be ported or written without SMP & Memory Protection, and it should reduce the number of fatal crashes we see, though I don't notice many crashes anyway right now.

MorphOS3.x appears to be making good progress without any plans to add full Memory Protection or SMP support, so my expectations aren't really any different for AmigaOS4.x.

Spirantho mentioned that he perceives an "End of the Road" for MorphOS development on PPC hardware, when they have completed support for the last few Mac PPC hardware choices that are not currently supported.  My perspective is very different, and I actually look forward to the day when the MorphOS Dev. Team members are finished with trying to port MorphOS3.x to any other models of PPC hardware, as that will mean that they will have more time to focus on creating or porting more interesting and essential software applications and/or games to MorphOS3.x, as well as further optimizations of the OS itself instead of working on new drivers for hardware which will not improve performance or functionality, but only let us install MorphOS on one more model of existing PPC hardware.

This is one area where I think that A-Eon and AmigaKit have hit a "home-run".  They see the value of now focusing their efforts on supporting the creation of more and better software to run on AmigaOS4.x, is their most important task.  Having the software you need or want is what makes using any computer useful.

I hope that the MorphOS Dev. Team members will soon have more time to work on new, or newly ported software.  More and better content/software applications and games, will probably do more for getting people excited and interested in using their Amiga, and/or Amiga inspired systems, than anything else.

I also hope that Soft-Core Motorola 680x0 CPU's running at speeds equal to, or exceeding 400MHz, loaded into FPGA chips on accelerator boards, inside of original Commodore Amiga computers, or stand alone FPGA Amiga clones, will spur on an increase of 68k software development.  That kind of jump in performance should be able to allow software tasks that could never before be accomplished on any Motorola 68k based computer.

AROS and all of it's variants appear to have some really sharp programmers working on it over the past few years and great progress seems to have been made, with more just around the corner, that will eclipse all of the first 10+ years of work on AROS combined.

What a great time it is to be involved in any part of our remaining community!  Certainly not a time to perpetuate the silly and childish fighting we see all too often.
« Last Edit: November 18, 2014, 12:07:04 PM by amigadave »
How are you helping the Amiga community? :)
 

Offline OlafS3

Re: One unified OS for the future?
« Reply #93 on: November 18, 2014, 09:27:36 AM »
I agree with Amigadave. The situation has improved in recent years with  many updates in the different camps and new software. Of course there is  a lot of to do and everyone can help, f.e. donating to bounties, help  testing and giving feedback to developers, make documentation like  tutorials for software, for optimizing and configuration of his  preferred OS and much more. There are always popping up new threads  requesting this or that from OS devs or the "community" instead to think  about what they himself can do. That sounds a little lazy to me,  instead making unrealistic requests people should do something himself.  That was what I did, I never expected anything from others and always  did what I could do myself (and will do that in future).

To the  topic, it is much too late for a "unified OS" because there are both  technical, legal and emotional reasons why this will never happen. What I  personal hoped for was that the camps would agree on a common  infrastructure to avoid unnecessary double work and speed up development  and make it easier to crosscompile. Common are (in my view)  PCI-support, USB, most of the system libraries and GUI system. The  sources should be opensource. All user-related components like desktops  and addons that are new and specific could have stayed closed. But I  understand now that even this idea is unrealistic. So people should  concentrate on what they have and help there.
« Last Edit: November 18, 2014, 10:24:27 AM by OlafS3 »
 

Offline itix

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 2380
    • Show only replies by itix
Re: One unified OS for the future?
« Reply #94 on: November 18, 2014, 09:49:00 AM »
Quote from: amigadave;777736
Edited out this quote of the private conversation information I should not have paraphrased out of context, please forgive my mistake.  AmigaDave

Well, no. Now it has been several years when I had Pegasos 2 and my memory is getting vague on these matters but there was great debate amongst users which configuration, one used by Linux or one used by MorphOS was better.

I cant remember which way around it was but IIRC in MorphOS 64-bit reads and writes were faster than in Linux but at expense of 32-bit read/writes (those are faster in Linux). Or was it vice versa, I cant remember anymore.

But it is strategy chosen by the MorphOS team and it is debatable which one is better. Linux or OS4 performance is not crippled in this regard.

Quote
Edited out this quote of the private conversation information I should  not have paraphrased out of context, please forgive my mistake.   AmigaDave

Of course because OS 4 was slower. If benchmarks were done on SAM460 or other platform there is no guarantee they would be using same configuration even on same hardware.

Quote
Spirantho mentioned that he perceives an "End of the Road" for MorphOS development on PPC hardware, when they have completed support for the last few Mac PPC hardware choices that are not currently supported.
That is funny statement.

Quote
This is one area where I think that A-Eon and AmigaKit have hit a "home-run".  They see the value of now focusing their efforts on supporting the creation of more and better software to run on AmigaOS4.x, is their most important task.  Having the software you need or want is what makes using any computer useful.

I hope that the MorphOS Dev. Team members will soon have more time to work on new, or newly ported software.  More and better content/software applications and games, will probably do more for getting people excited and interested in using their Amiga, and/or Amiga inspired systems, than anything else.
Uhm, but this is what MorphOS team is doing and what Hyperion is not doing. There is bunch of useful software developed or ported by the MorphOS team, starting from Odyssey web browser to SDL ports. Sketch, Transfer, Scandal, Scribble, RemoteShell, Jalapeno, Jukebox or VPDF are examples from the MorphOS ISO. And dozens of ported or new libraries making porting and writing software easier. And there is new and ported software released externally.
« Last Edit: November 18, 2014, 12:12:33 PM by amigadave »
My Amigas: A500, Mac Mini and PowerBook
 

Offline spirantho

Re: One unified OS for the future?
« Reply #95 on: November 18, 2014, 09:53:36 AM »
@OlafS3

You mention something which would be very useful, actually.
I can see that for many parts, there are similarities rather than differences, but for some bits such as the PCI and USB that you mention, the APIs are quite different. If they were standardised across platforms it would make driver development much easier across platforms. Even graphics APIs are separating more and more now.

We should celebrate the differences in the underlying OS between MorphOS, AmigaOS and AROS, while striving to keep software flowing on all the OSes... but as the APIs move away from each other this will get harder and harder.

Ideally I would like there to be an independent "Amiga-like" council which would define APIs - each OS would contribute submissions via RFCs to the multi-platform council which would then ratify or deny that submission before it became standard.

This could never happen, though, because each of the OS owners would say "Why should we? We're a different OS - we're not responsible for the other OSes. We'll do what we like, thanks".... plus in my experience there would be precious little agreement about how the APIs should work - but it would be nice.
--
Ian Gledhill
ian.gledhill@btinternit.com (except it should be internEt of course...!)
Check out my shop! http://www.mutant-caterpillar.co.uk/shop/ - for 8-bit (and soon 16-bit) goodness!
 

Offline spirantho

Re: One unified OS for the future?
« Reply #96 on: November 18, 2014, 10:00:26 AM »
Quote from: itix

Quote from: AmigaDave

Spirantho mentioned that he perceives an "End of the Road" for MorphOS development on PPC hardware, when they have completed support for the last few Mac PPC hardware choices that are not currently supported.

That is funny statement.


Just to clarify - what I meant is that once all the Mac PPC models are supported, they're going to be stuck with increasingly ageing hardware which is going to get more and more obsolete. They're going to need to change to another ISA such as x86 or ARM if they're going to stay at all current - I don't think there can be any argument to that.
If they don't, then in the future AmigaOS will be using multi-GHz multi-core low-power brand new hardware, AROS will be using brand new low-cost x86 hardware, and MorphOS will be stuck to ancient Mac Behemoths without any support for the current technologies - that would be a bad thing for MorphOS.
--
Ian Gledhill
ian.gledhill@btinternit.com (except it should be internEt of course...!)
Check out my shop! http://www.mutant-caterpillar.co.uk/shop/ - for 8-bit (and soon 16-bit) goodness!
 

Offline OlafS3

Re: One unified OS for the future?
« Reply #97 on: November 18, 2014, 10:36:10 AM »
Quote from: spirantho;777744
@OlafS3

You mention something which would be very useful, actually.
I can see that for many parts, there are similarities rather than differences, but for some bits such as the PCI and USB that you mention, the APIs are quite different. If they were standardised across platforms it would make driver development much easier across platforms. Even graphics APIs are separating more and more now.

We should celebrate the differences in the underlying OS between MorphOS, AmigaOS and AROS, while striving to keep software flowing on all the OSes... but as the APIs move away from each other this will get harder and harder.

Ideally I would like there to be an independent "Amiga-like" council which would define APIs - each OS would contribute submissions via RFCs to the multi-platform council which would then ratify or deny that submission before it became standard.

This could never happen, though, because each of the OS owners would say "Why should we? We're a different OS - we're not responsible for the other OSes. We'll do what we like, thanks".... plus in my experience there would be precious little agreement about how the APIs should work - but it would be nice.

I have a alternative idea. In "normal life" I am programming on Windows using Delphi in different variants and Visual Studio. Common is that all are based on class libraries that hide the internals. As a application programmer I do not care about Win32 or other APIs, I use the classes of the library. The only chance I see (besides standardizing the APIs) would be to use a kind of Amiga class library that hides the differences so you could crosscompile a source without needing to make specific changes. The only problem is you need that for every language and you need experts who adapt the needed changes for every platform. I am myself (as written) a Pascal fan so Free Pascal (that is now available for 68k, Aros X86 and MorphOS, for AmigaOS there is a older port available) are first choice but that is a personal thing. Amiga-E is a good candidate too with many includes available and of course C. Solutions like Bytecode similar .NET are propably too complicated to do.

To the idea... the class library(s) should be open source so everyone can contribute. The big advantage... easy to crosscompile and changes would only be needed one time (in the class librarys) and not in every application. And it would be easier for outsiders to start on the platform.
« Last Edit: November 18, 2014, 10:46:41 AM by OlafS3 »
 

Offline spirantho

Re: One unified OS for the future?
« Reply #98 on: November 18, 2014, 10:46:29 AM »
@OlafS3

The other problem with abstraction layers like that (or even bytecodes like .NET) is that of speed. We will always suffer from a lack of speed compared to Windows machines, and as programs get heavier and heavier in their resources it's going to become more and more impractical. We need to grab as much power out of our "Amiga" machines (whatever they are) - the primary advantage we have is that we have much more lightweight operating systems. If we go the way of bytecode and abstractions we lose that strength entirely.

Abstraction is great for porting software, but useless for ekeing the most power out of the hardware, which is especially necessary for Amiga-like systems (particularly so when porting MAME, trust me :) )
--
Ian Gledhill
ian.gledhill@btinternit.com (except it should be internEt of course...!)
Check out my shop! http://www.mutant-caterpillar.co.uk/shop/ - for 8-bit (and soon 16-bit) goodness!
 

Offline OlafS3

Re: One unified OS for the future?
« Reply #99 on: November 18, 2014, 10:53:38 AM »
Quote from: spirantho;777748
@OlafS3

The other problem with abstraction layers like that (or even bytecodes like .NET) is that of speed. We will always suffer from a lack of speed compared to Windows machines, and as programs get heavier and heavier in their resources it's going to become more and more impractical. We need to grab as much power out of our "Amiga" machines (whatever they are) - the primary advantage we have is that we have much more lightweight operating systems. If we go the way of bytecode and abstractions we lose that strength entirely.

Abstraction is great for porting software, but useless for ekeing the most power out of the hardware, which is especially necessary for Amiga-like systems (particularly so when porting MAME, trust me :) )

yes abstraction has some cost but in my view the advantages outweigh the disadvantages. One big advantage is that there is a higher chance that developers from outside start with it. I have contact to a lot of former amiga-developers that were known for their projects. Unfortunately most of them have long left the platform and are not interested to return. For a real new developer with no previous experience the learning curve is very steep, the start difficult (missing modern development environments, not enough documentation, not many tutorials, no class libraries and so on). If they could use at least a standardized class library start would be much easier. It would be even useful to have a standardized class library that is implemented for different languages so you could transfer your knowledge and would only need to learn another language.

Might be that there are very specific projects that need every bit of power but for most applications that would not be a problem. Bytecode was only one example for crossplatform development, it would be too complicated to do and needed too much manpower for our small community.
« Last Edit: November 18, 2014, 11:02:34 AM by OlafS3 »
 

Offline itix

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 2380
    • Show only replies by itix
Re: One unified OS for the future?
« Reply #100 on: November 18, 2014, 10:54:30 AM »
Quote from: spirantho;777745
Just to clarify - what I meant is that once all the Mac PPC models are supported, they're going to be stuck with increasingly ageing hardware which is going to get more and more obsolete. They're going to need to change to another ISA such as x86 or ARM if they're going to stay at all current - I don't think there can be any argument to that.
If they don't, then in the future AmigaOS will be using multi-GHz multi-core low-power brand new hardware, AROS will be using brand new low-cost x86 hardware, and MorphOS will be stuck to ancient Mac Behemoths without any support for the current technologies - that would be a bad thing for MorphOS.


That is going to take several years and there is always possibility that MorphOS is ported to some future AmigaOne hardware or gets ported to different CPU arch.

I just found it funny because there is no future for PowerPC on desktops. If A-eon calls it a day it is the end of AmigaOS 4.
My Amigas: A500, Mac Mini and PowerBook
 

Offline itix

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 2380
    • Show only replies by itix
Re: One unified OS for the future?
« Reply #101 on: November 18, 2014, 11:01:09 AM »
Quote from: spirantho;777748
@OlafS3

The other problem with abstraction layers like that (or even bytecodes like .NET) is that of speed. We will always suffer from a lack of speed compared to Windows machines, and as programs get heavier and heavier in their resources it's going to become more and more impractical. We need to grab as much power out of our "Amiga" machines (whatever they are) - the primary advantage we have is that we have much more lightweight operating systems. If we go the way of bytecode and abstractions we lose that strength entirely.

If not losing on speed then we are losing on application development. It is so much faster to type programs in C# using .NET than using relatively low level languages like C. When C programmer is working on 0.7 beta C# programmer is already finalizing new features to forthcoming 3.1 release.

And speed is not so much important anymore when we are at 1GHz+ range. Most of time CPU is running almost idle wasting its potential.

We are already using bytecode in sense how we run 68k programs on PPC and it is fast enough. We just dont get advantages of .NET with it.
My Amigas: A500, Mac Mini and PowerBook
 

Offline spirantho

Re: One unified OS for the future?
« Reply #102 on: November 18, 2014, 11:35:26 AM »
It depends on what you want to do.
If you want to encode (or decode) video, play MAME, that sort of thing, then using bytecode would be impossible.
I know what you mean, though - for less demanding applications, high level programming languages like C# or Java can speed up the writing massively - but as usual different applications have different requirements, so we can't force people to use high-level code as it could be disastrous (especially for things like device drivers).
--
Ian Gledhill
ian.gledhill@btinternit.com (except it should be internEt of course...!)
Check out my shop! http://www.mutant-caterpillar.co.uk/shop/ - for 8-bit (and soon 16-bit) goodness!
 

Offline amigadaveTopic starter

  • Lifetime Member
  • Hero Member
  • *****
  • Join Date: Jul 2004
  • Posts: 3836
    • Show only replies by amigadave
    • http://www.EfficientByDesign.org
Re: One unified OS for the future?
« Reply #103 on: November 18, 2014, 12:04:30 PM »
Quote from: OlafS3;777742
......... So people should  concentrate on what they have and help there.

Nice post Olaf.  I did not quote the whole thing, but give you a +1 for all of what you wrote.

If everyone just enjoyed what they have chosen to use and concentrated on how they can help improve any part of our community, things would be much better than they are now and programmers would be more encouraged to work on new code for any of our platforms.  When there is less fighting between users, there also seems to be more cooperation between 3rd party developers, and more software that gets written or ported to different Amiga inspired platforms.

@everyone,

I want to take this opportunity to apologize to Spirantho for paraphrasing some of our private discussion, as it has hung him out on a limb for possible criticism by some users or developers, without the benefit of the context of our entire discussion.  I was going to come back here and just delete that part of my post, but some of you have already quoted what I wrote and commented on it with posts aimed at Spirantho.  His suggestion to copy and paste our private discussion to the forums as an example of how these differences can be discussed without any fighting or hostile words was rhetorical and not literal, and I should not have paraphrased what he wrote out of context, or without his permission.  Please do not attack him for my mistake.
« Last Edit: November 18, 2014, 12:15:31 PM by amigadave »
How are you helping the Amiga community? :)
 

Offline itix

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 2380
    • Show only replies by itix
Re: One unified OS for the future?
« Reply #104 from previous page: November 18, 2014, 12:05:41 PM »
Quote from: spirantho;777754
It depends on what you want to do.
If you want to encode (or decode) video, play MAME, that sort of thing, then using bytecode would be impossible.
I know what you mean, though - for less demanding applications, high level programming languages like C# or Java can speed up the writing massively - but as usual different applications have different requirements, so we can't force people to use high-level code as it could be disastrous (especially for things like device drivers).


Bytecode is not solution to everything but you could write a MP3 encoder in C# and use encoder libraries written in C.
My Amigas: A500, Mac Mini and PowerBook