Related
as the title says...?
I've been using Dutty's for the past few months, but it seems like ROMeOS is the best these days...
Probably the same one as the answer to the last time this question was asked... Oh, about 20 minutes ago. Please use the search. That's why it's there.
Seriously though, Best rom? Good question. Many are geared towards different ways of using the device. Best advice is to READ descriptions and threads like the rest of us and do your own research.
BAM BAM
shot down
seriously, these posts are the reason i have so much trouble finding information and researching...too many ppl post useless threads like this
JPS4 said:
BAM BAM
shot down
seriously, these posts are the reason i have so much trouble finding information and researching...too many ppl post useless threads like this
Click to expand...
Click to collapse
Agreed - when I got my TyTN II I also had the same question.
Well the answer is simple - LOTS OF RESEARCH!!!
there is not the best one in general, but one that fits your needs.
So please read description of each ROM
elite-fusion said:
as the title says...?
Click to expand...
Click to collapse
Like the others said - and it of course depends on your preferences (i.e. type of apps, performance, appearance, etc.)
A good rule of thumb (ALL NOOBS TAKE THIS HINT!!) would be to look at the postings for recent ROMS and see how many responses there are to the thread. It could be a red herring if there have been a few bugs, but generally it indicates a popular ROM and from reading (yes read the initial posts please!) you can quickly determine if this might be a ROM for you. The responses from users will highlight any issues that may be specific to the software you'd like to run.
Maybe the mods can close this now - or maybe create a "Which ROM should you flash - read this first" Sticky that paraphrases this to prevent this weekly question.
if you are looking for a multimedia ROM (stable) i suggest Dutty's April 29 ROM
if you are looking for fast and fancy ROM i suggest ROMEOS 3.5
here ya go
But still like said above it has to be a ROM that fits ur needs.
cheers
Find the Best Rom! Ask 10 cooks get 10 best Roms
First Hard SPL your phone find a rom offering. Read what others say about it, then if it sounds like something you might like, Flash it. Then try another and another and keep going until you can answer that question for yourself. READ! for your self and learn. The bottom line is the best rom is a myth! it only can be the best if you say it is so. What I believe to be the Best you might Flash and think it sucks. Do some work on your own and learn! WiKi, WiKi, WiKi!
Hyperdragon ..
You can try Hyperdragon. I have been running it for quite some time now and have found it to be very stable and without almost no glitches..
Best rom
elite-fusion said:
as the title says...?
Click to expand...
Click to collapse
Check them all out, best rom depends on your needs, check out this link...
http://forum.xda-developers.com/showthread.php?t=410975
for donation you can have a rom cooked to your own specs. Getting you the best rom!!!!!
Try ROMeOS V3.5
It's fast, stable and the support of Hang.Tuah is great.
These threads are popping up all over lately. Cany anyone do their own research anymore?
Hi all!
I'm new here. I bought a new (half year old) kaiser with a cooked rom. First I restored the original wm 6.1 rom. But this is very slow. I searched and found a lot of rom but I can't choice. I search a rom which is small and fast include java and live messenger and better camera driver (too noisy and after sunset it is taking a picture up to 10 seconds!). I found a new display driver under development, on this page. I would like to this driver be part of the cooked rom, if the driver is working property (i hope this is understandable ). So my phone is original non-SIM-locked and the bootloader has cracked. one thing: on the original rom the tcpmp don't start, but with the cooked rom it ran. I don't need wm 6.5 but if that is better no problem.
thanks for your help!
I hope my first thread is created at the good part of the forum
Firstly,
Welcome to the forum! This is the right part of the forum for Kaiser ROM, however ...
Secondly,
You'll need to do a lot of reading, and decide based on that. As a newbies, I did ask this question too, and the answer came back: no recommendation can be given, each must take each' journey.
You can make the decision by reading the thread of each ROM, read the responses, and clarification by other users.
It takes a lot of hardwork to read, and it takes more hardwork for the chef's to cook a ROM that works well! So, my suggestion is to read more and ask less.
Happy hunting
(and mod, please shut down the thread)
ROMs
I can't say one is better than the other. I've tried quite a few ROMs and have settled on TPC Elite, however that is what works best for my purposes. The previous answer to your post is correct, lots of reading and then make the decision on your own.
Once you have HardSPL installed (version depends on the ROM your flashing as I've read), you can flash a different ROM every day like you decide what shirt to wear each morning. It's quite awesome!
thx all!
im on it. i am reading the rom infos since i registered here. but i thinked i found somebody who is minimalist like me
Anryl ROM is great but now anryl stop making ROM for Kaiser
so now I'm stuck with TPC Elite ROM... great ROM. so I recommend this one... try V4.
better you read the tutorial first about upgrading ROM, radio, SPL etc..
if i seen good (direct from hungarian ) the TPCElite needs hardslp v3.56 and i have spl-3.56.Hard CPLD-8 so this is passed. total 100mb ram? its better than oem (85) i will try this
i confused the 3d graphic driver is included?
Try any of the latest ROM out there, then stick to the 1 without problem I almost bricked my kaiser last time flashing hardspl. so be careful.. Dun flash unneccesary to much
sorry if this has been said before, but it would be easier if there were 2 forums for the 2 different Sapphire types.
edit: added a 10-day poll, enough time for everyone to put their opinion forward
+1 I agree with you.
I agree too!
+1 This would be great. Even if the posts could be tagged 32A or 32B
Agreed!
Save some confusion.
quite agree with you!!
not sure why this is necessary if ROM creators tag their threads with the correct version.
Well they need to tag it at the start, rather than the enb of the title eg.
[32A][ROM][PORT] xxxxxxxx v 4.2.3.1
rather than
[ROM][PORT] xxxxxxxx 32a v4.2.3.1
It makes it much easier to read rather than having it hidden somewhere in the title
Won't be long now and we might get some truly universal roms going.
I know Cyanogen's working towards it.
Until then.. it's not like there's a lot of difference - only two files really.. boot.img and wlan.ko.
If all the rom developers clearly marked their roms as 32a/32b then it wouldn't matter so much.
Radix999 said:
Won't be long now and we might get some truly universal roms going.
I know Cyanogen's working towards it.
Until then.. it's not like there's a lot of difference - only two files really.. boot.img and wlan.ko.
If all the rom developers clearly marked their roms as 32a/32b then it wouldn't matter so much.
Click to expand...
Click to collapse
Exactly my thoughts. There is a big discussion on this and even if this doesn't happen I can't believe that people are so lazy that they don't read the first post of a thread to distinguish if the ROM is 32A or B!!!
Radix999 said:
Won't be long now and we might get some truly universal roms going.
I know Cyanogen's working towards it.
Until then.. it's not like there's a lot of difference - only two files really.. boot.img and wlan.ko.
If all the rom developers clearly marked their roms as 32a/32b then it wouldn't matter so much.
Click to expand...
Click to collapse
Exactly and in the meantime if the forums were separated there's the danger one or the other might miss out on something the other is doing. Much better everyone sees everything.
-1
I don't like this idea: many topic are shared among the two models (all is related to the applications!). Now it is already a mess that I'm loosing great topics on the Dream's forums.
In the next future (I hope) there will be many firmware that can works on both the models (even on the Dream): look at the Cyanogen.
The use of the tags is good enoght!
+1 agree
the rooms must be in separate threads, but maybe the apps must be in only one for all Android mobiles.
Is difficult to know now for what version of Magic is a post (no only roms, also related post answering about)
Now I think is too late.. we just have to organize each others better like suggested before...
Do you imagine the work will have a moderator of this forum moving all the threads?
-1
I don't like the idea because I have to post everything twice when I release something for both sapphire's.
I do like the idea of the tagging the threads.
+1 4 tagging
Better tagging will do the job.
Amon_RA said:
-1
I don't like the idea because I have to post everything twice when I release something for both sapphire's.
I do like the idea of the tagging the threads.
Click to expand...
Click to collapse
-1
exactly...
i agree because there is no common thing
at314 said:
i agree because there is no common thing
Click to expand...
Click to collapse
Almost everything is common.
Better tagging, or rather better reading of the tagging is the answer. Most threads are properly tagged, I think the problem is more to do with people not reading the tags/titles properly.
Paying a bit more attention is the answer.
+1 for the guy that says: WTF, just RTF Topiclines a bit better before whining.
If you can't read 32A or 32B, get your eyes examined
To that end, don't visit the forums while drunk, doped or very sleepy, it'll prevent topics like this ever getting started.
Peace out!
I think its a good idea, Posted in these forums as its this development one i think it should be done on.
If this was done then i reckon there will be less bricking going on!
How hard is it to Read [Rom] ( 32b or 32a )
Plus, I make a few that is 32a roms with 32b, I'm not going to waste my time to manage 2 different threads, sorry that's how I feel.
I think as long as it is required for ROM posting threads to be clearly labeled [32A] OR [32B], that is good enough.
Isn't the only thing that can permanently brick your device the SPL? So we just need to split that to avoid confusion
yah... well
n00bs are n00bs and if your too dumb to read you deserve a bricked phone
that being said i think it would declutter forums slightly
i mean
theres split forums for cdma and gsm versions of devices
you think that different motherboards would be a big enough difference to split the forums ?
i dont care either way it would just make it less cluttered i think
Well you guys who have experience may not think its a good idea but what about people who want to learn and end up breaking phones? or like myself break a phone then get too scared to try again!
I am (was) new to this whole smartphone thing not so long ago, did my reading and research, SPL flash, ROM stuff, all went perfectly smoothly. Coming from another large tech forum with hundreds of new members daily, you will always get people who don't bother reading the stickies/guides/whatever. It's furstrating but that's just the way it is, not everyone have used an online forum before.
Perhaps a better idea would be for someone to volunteer to put together a complete guide as I often find information rather scattered around here. Yes there is a sapphire hacking wiki, but the threads it links to doesn't really explain stuff any better either. I managed to figure my way through though.
If you are willing to flash ur phone then you should be willing to read. and you should be reading the whole first post or two depending on how many the dev that opened the thread is using. Its just spreading out information. Already have to go back and fourth to dream and sapphire to make sure that we dont miss anything.
eugene373 said:
How hard is it to Read [Rom] ( 32b or 32a )
Plus, I make a few that is 32a roms with 32b, I'm not going to waste my time to manage 2 different threads, sorry that's how I feel.
Click to expand...
Click to collapse
so can we not have a simple way of doing a title
cause this is what we get
[ROM] eViL HeRo v3.0 COMPLETE BFS 32B +/-A2SD [10/12/09-UPDATED]
[ROM](32A / 32B) Hero3G UNI Final w/ Theme Flavors 10/20/09
[ROM][32a] CyanogenMod 32a Port 4.1.9999 [update Oct 19] [Now with BFS 304!]
[Updated 10/17/09][ROM][32B/MT3G] OTPA Hero - v.1.4.1
[ROM] [32A & 32B] [10-Oct-2009] RAv1.6.2 - DONUT
[ROM][G1/MAGIC:32B] Hero by Maxisma v1.8 [13/OKT]
[Rom] [32b] Blur for MyTouch / G1 with Working BlueTooth 10/19/09
[ROM] KiNgxKxROM Version 1.9 "Not My Goodies" <10/17/09> 8:30pm PST
its a bit daunting for noobs
[ROM 32B] [ROM 32A] or [ROM](for either)
release name+system then version+date
so
it could look like this
[ROM] eViL HeRo v3.0 (10/12/09)
[ROM] Hero3G UNI Final (10/20/09)
[ROM32a] CyanogenMod 4.1.9999 (10/19/09)
[ROM32b]OTPA HERO v1.4.1 (10/17/09)
[ROM] RA DONUT v1.6.2 (10-Oct-2009)
[ROM] Maxisma Hero v1.81 (10/13/09)
[Rom32b] Blur for (10/19/09)
[ROM] KiNgxKxROM Hero v1.9 (10/17/09)
and all the new bits and stuff inside the post
we could split the whole Sapphire android development part into 2
1. working roms
2.dev roms beta roms and everything else
just an idea
I think this issue could be properly resolved simply by ensuring the threads are explicit. This means having the thread accurately titled, but also ensuring that the content (downloads) is explicitly labeled and maintained. Often times the title indicates both a 32a and 32b version available, but the actual content (the correct content) can be difficult to find in the posts.
personally id like split forums for ease of reading.
Its not that i cant get the correct rom it would be 10x easier if i knew a section would be devoted to 32A only.
That way i can scroll through all threads knowing these roms are available.
It would save time and im all for that =)
I completely agree with this. It'll prevent bricked phones. Its that simple.
Zarboz said:
yah... well
n00bs are n00bs and if your too dumb to read you deserve a bricked phone
Click to expand...
Click to collapse
You might want to consider that it's not always a question of whether or not ppl are n00bs, but I'm sure there are 'more than 1' that have english as a second or maybe even third language...
Although english isn't difficult for me (as a second language), I have been reluctant to try a ROM here and there due to not quite catching if it was A or B.
Splitting the forum in A and B would be helpfull for the ones that aren't that skilled in the english language, but I'm sure 'tagging' the title of a ROM thread to ensure if it's A or B, like some already do would suffice
No!
i think myself and a alot of others have no issue in reading 32A 32B. alot of roms posted on here anyway are clearly labelled so i dont see what the issue is?
For those people who dont have their roms clearly labelled they should take note
It's been asked before, the same result came out of the poll as seems to be the case at the time of writing - but the request still got a blank.
Personally, I think there'd be more logic in making the existing Sapphire board a 32A board only, and merging the 32B area with the Dream area. ROM-wise, all you need to turn a Dream ROM into a dual Dream/32B ROM is to copy init.trout.rc to init.sapphire.rc. Job done. Basically the Dream is a Sapphire 32B with less internal storage plus a keyboard. Whereas the 32A is a rather different animal.
I say no
Their are ROMS that supports both and as long as the developer has whether it is a 32A or 32B is good enough. SPL's should be separated though.
Making the case for NAY
NOTE: I am brand new to smartphones, and recently had to go through the learning curve of how to fix the SPL, root and load new firmware. Not new to tech though.
It does not really matter what the users, especially the noobs want as it is mostly a development forum. Why should the devs have to got out of their way to cross post, monitor multiple forums and jump through hoops to help out someone who can't parse 32a or 32b out of a subject line. If someone cannot figure out how to do something to a fairly expensive, easily bricked, bit of electronics kit, then perhaps they should not be doing it.
It is reasonable to expect people to have a certain baseline of knowledge, or to do their homework (ie google for it) before doing something as complex as overwriting the firmware on a portable computer (which a smartphone most assuredly is).
Speaking as someone who has done support, run large support organizations, and been involved in tech for almost 40 years, it does not matter how tidily and nicely you present the info and how much you hand hold and spoon feed, people will continue to amaze you with stupid (as in the answer is in the title, let alone the body of the message) questions and new and novel ways to really mess up. You cannot find a way to presenting the info so people will not misunderstand or make mistakes. It is impossible to make things fool proof since fools are so good at what they do. Please lets not go down that rabbit hole...
If the site decides to put a bunch of posting rules in place to try and force posters to follow some rigid subject line and content standards, the doers (devs and senior folks who answer most of the questions) will just go somewhere else. They are doing this as a hobby.... and are sharing their work and unpaid support time because they enjoy it. Expecting them to adhere to your idea of "the right way of doing things", and especially to change what fundamentally is their dev forum is rather selfish and somewhat foolish... and doomed to failure.
I have watched a number or forums, newsgroups and BBSs (told you I was old) grow, become popular and then self destruct as latecomers decided to impose their vision of "how things should be done" or the signal to noise ratio just became to horrible as the demands for hand holding and help overwhelmed those trying to help and contribute.
bjtheone said:
NOTE: I am brand new to smartphones, and recently had to go through the learning curve of how to fix the SPL, root and load new firmware. Not new to tech though.
It does not really matter what the users, especially the noobs want as it is mostly a development forum. Why should the devs have to got out of their way to cross post, monitor multiple forums and jump through hoops to help out someone who can't parse 32a or 32b out of a subject line. If someone cannot figure out how to do something to a fairly expensive, easily bricked, bit of electronics kit, then perhaps they should not be doing it.
It is reasonable to expect people to have a certain baseline of knowledge, or to do their homework (ie google for it) before doing something as complex as overwriting the firmware on a portable computer (which a smartphone most assuredly is).
Speaking as someone who has done support, run large support organizations, and been involved in tech for almost 40 years, it does not matter how tidily and nicely you present the info and how much you hand hold and spoon feed, people will continue to amaze you with stupid (as in the answer is in the title, let alone the body of the message) questions and new and novel ways to really mess up. You cannot find a way to presenting the info so people will not misunderstand or make mistakes. It is impossible to make things fool proof since fools are so good at what they do. Please lets not go down that rabbit hole...
If the site decides to put a bunch of posting rules in place to try and force posters to follow some rigid subject line and content standards, the doers (devs and senior folks who answer most of the questions) will just go somewhere else. They are doing this as a hobby.... and are sharing their work and unpaid support time because they enjoy it. Expecting them to adhere to your idea of "the right way of doing things", and especially to change what fundamentally is their dev forum is rather selfish and somewhat foolish... and doomed to failure.
I have watched a number or forums, newsgroups and BBSs (told you I was old) grow, become popular and then self destruct as latecomers decided to impose their vision of "how things should be done" or the signal to noise ratio just became to horrible as the demands for hand holding and help overwhelmed those trying to help and contribute.
Click to expand...
Click to collapse
You should def get the nobel peace prize for this one lol
Well I voted YES but so far the thread titles have been pretty good at stating what the ROM/content is meant for.
Maybe be just a standard or template for thread titles and first post is all we need?
I think it's a good idea to have 2 forums for different roms...
But it could be to something like:
[ROM][32B] blablabla (Date)
It would be a lot more easy to know when a rom was updated and for what system is 32B or 32A...
This NOT ment to be *****ing, I AM grateful for all the great work being done, But i do WISH every single dev could include this in their first post in their ROMs thread:
-What the ROM is based on (HTC framework, ADP, ADP with Sense from Dream, Sense from Hero etc.)
->What works (or not) of:
* LED
* bluetooth
These are common problems with HERO ROMs, and if every dev posted this info, it would be great. For me non-LED= not usable, and for some periods of time (ie. when I'm driving much), so is no BT
->Included apps.
*Especially important are sms-spamming apps such as myfaves - coud be critical to know about.
->recommended compache settings, swapiness etc, what is used in ROM as standard for these values.
We see every Hero-thread filling up with questions about BT, LED, what HERO-version, and what framework, and whatnot. Taking 2mins to post this info could help save so much time,and so much spam/question in the ROM thread.
Apps added/removed and the other stuff is also higly relevant to non-HERO roms.
Again, this is constructive criticism aka a humble suggestion, not an angry demand from some jerk with e-penile problems. (Or so I'd like to believe, at least.)
If anyone has any suggestion as to what other info you would like to see in a ROM announcement? Post it here, maybe we can "help" the devs out by making a complete template we would like them to follow. Input from devs highly appreciated too, ofc.
I know there are toher things that shoul also be listed, such as SPL and radio required etc., although I believe almost everyone includes it. Most devs include most of the items on the list too, but many do not include all of it.
Also, I am sorry for posting this in this category, but this is where the ROMs are posted and the devs can see it.
I hope this thread has its place here. Different people are lokking for different things, and both the user and devs benefit from the user knowing what they get. (It would hopefully limit the number of "spam" questions from users if the first post contained all this information, we know many people are afraid of the search button. Also, it would be easier to wield the ban hammer on people whoe doesn't even bother to look at the simple list in the first post, and waste other peoples time.)
If a dev included enough information, ROM lists with information abut different ROMs would also be much easier to maintain for the good people making them.
It may make things more organized, but it means devs have to update the list, and pay less attwntion to -actual ROM development.
And in my opinion, a little trial and error never hurt anyone.
TermyJW said:
It may make things more organized, but it means devs have to update the list, and pay less attwntion to -actual ROM development.
And in my opinion, a little trial and error never hurt anyone.
Click to expand...
Click to collapse
This is TRUE!
I so hope that Hero ROM's on donut are much more snappier! I'm addicted, I want a ROM to use for a few months! Hehe.
Yeah, it would be nice if there was a template developers could follow for posting. It would make thing's so much smoother.
Possibly in the title of the post have;
[ROM] [SENSE] "Title Here"
[ROM] [PULSE] "Title Here"
[ROM] [MOTOBLUR] "Title Here"
[ROM] [1.6] "Title Here"
[ROM] [1.5] "Title Here"
I agree with the OP there are times where i i can't flash 5 different ROMs in a day and i skip over some because of lack of info and screenshots. Maybe the community can build a template that the ROM devs can use?
damnitpud said:
I agree with the OP there are times where i i can't flash 5 different ROMs in a day and i skip over some because of lack of info and screenshots. Maybe the community can build a template that the ROM devs can use?
Click to expand...
Click to collapse
Are you thinking about getting back into making themes?
not gonna happen
jubeh said:
not gonna happen
Click to expand...
Click to collapse
word im too lazy
they already spend there time developing the roms, i dont think they have the time to make the "proper layout"
Binary100100 said:
Are you thinking about getting back into making themes?
Click to expand...
Click to collapse
I have been playing around with some images, made changes for my own phone but haven't done much else. I did just get laid off from my job so if i go the unemployment route you will definitely see me more in these forums. If i can't find a job soon i plan on getting into Java programming(i have a few app ideas) and possibly making my own ROMs. But we have to see where the job market takes me.
To stay on topic, the devs do spend a lot of time dev'n and having a template in a txt file would make posting easier for them. I have made a few threads and i can tell you making a layout for a post isn't that easy and is not much fun. If we can make an empty template that they only have to fill in their info...they would be doing the same amount of work on the post, just easier cause its all laid out for them.
We would need a sticky for it and have the devs vote on it or something.
That's a great idea it would be so much easier plus people won't be trashing threads with dumb ass questions is this for G1? Does this work or does it still do that and so on....
I mean before they upload the Rom they know most of the bugs so just saying known issues r these and that would help and just knowing what's new in the release doesn't help just confuses most of the noobs here...I'm one of them.
A little off topic but I'm a recruiting officer in a PC gaming community and I review clan applications, there were times when main application was down so I just made a sticky Thread with a template of the application to fill up and post it as a new thread
I mean look all of the devs pretty much do that already anyhow, every thread they make look exactly as the other 1 we just need a clean template that they all could use and just made it as a sticky thread and lock it so every1 could use it.
Zarboz said:
word im too lazy
Click to expand...
Click to collapse
If you're making a ROM and posting it on xda, you obviously want other people to use it.
If the first post is sloppy and not informative or up to date. Less people will use your ROM. Thus, less people will test it. Therefore, you won't be able to figure out the bugs. If you're sloppy with info, you'll lose, not us.
Something that should be standard:
A proper title like suggested earlier such as [ROM] [1.6 - Pulse] [******]
(none of that [ROM] ***MghtyMax 1.9.1*** "WHAT A FEELING!" stuff....Sorry, but it's just plain horrible.)
Another thing should be a list of features, things that work, things that don't.
Screenshots are also very nice and descriptive. A lot of new users might not know what Pulse, Hero, etc. looks like.
If you take the time to work on a ROM, you have the time to work on a nice looking first post. Don't half ass your work. It makes you look unprofessional.
I agree with the first poster, also MD5 hashes would be nice.
As damnitpud mentions, this would probably make it easier for devs, not harder. This is about *not* forccing them to make the proper layout themselves, but serve as a pre-made basis for them to fill in. In ready made bb-code ofc.
Since the mighty max-rom was brought up, this is noe ROM i did not download and flash immedeatly beacause I couldn't find info about BT working or not. Also would like to know if it were the SENSE from Dream or Hero. And some other details.
As I have time to sit down and flash my phone maybe two days a week, tops, I would like to know what I want to try beforehand. I also don't want to read four hundred post with questions that sometimes are answered in the first post, sometimes in the thread, sometimes not at all. But IF they had been answered in first post - and especially if it were in standard list that all/most devs used, it would be hard to miss it, and save a lot of stupid and/or lazy people nagging.
md5 hashes is absolutely something that should be on such a list, ohnoezmahfone. That is certainly lacking, and quite important for people with a good-for-nothing-ISP or net by 3G modem etc.
Someone make up a template. There will always be someone who will volunteer to do it for the developer.
All great ideas.
Especially for the sake of SEARCH.
Example:
I enter a search for "bluetooth working hero" and up pops 4000 unhelpful results most where 1000 noobs are asking if it works or not without doing the proper research in the prior posts.
An all informative 1st post would reduce this and the unnecessary flaming that follows (also part of results)
Also, it would also be real nice if everyone keep their personal lives to themselves.
Noone cares if your "flashing [other irrelavant ROM] now because BT aint working for Hero yet. This also shows up in results.
If I want you to kno whats on my device, i'll put it in my sig
I know i just made "BT working Hero" one more result longer [4001] but i had to vent. Sometimes searching can be very annoying and cumbersome.
Less results means less hassle for devs and users.
Once again, great ideas