pouët.net

erm, exactly what i said in the sentence: update the article about bytetro coding that already exists in in4k to 2016 based on info that you been putting into sizecoding.org.

damn, is my written english that bad?! :D

i don't see sizecoding.org as a any sort of slight against in4k whatsoever. :)

Yes, I'm damn sure that "it" referred to "in4k" in ps' quote.


FWIW I wanted to add articles and tutorials on www.256b.com, but I didn't feel entitled to enroll more people and turn the site into a mix between Pouet.net and Sizecoding.org as the site wasn't really mine; Insomniac/Neon gave me ftp+db access because he didn't have the time to maintain it anymore.

Thank you folks for in4k.github.io and sizecoding.org \o/

Oh, okay, I misunderstood. Thanks for clarifying :-)



No, my reading comprehension is that bad ;)

That's ok, I also thought "it" referred to "info that you have been putting into sizecoding.org". The word usually refers to the last subject written, so when we read "it" we popped "sizecoding.org" off the stack. :) There should be a word for "it, I mean the next-to-last thing I said".

great initiative!

@phoenix: Try German, or any other other language with gendered nouns :-) Having items hashed into three buckets (instead of the single universal “it” bucket) makes collisions much less likely.

I do feel the same way. I think at this point its more a strength to have a direct separation between the two fields.

I also feel that an important difference are their operating systems. In DOS, <1k intro coding dont need consider Portable Executable or a MZ executable programs. That is have no need for headers. There is no dynamic link library hell, hashing and/or ordinal lookups etc. Win32/win64 APIs are useless in DOS, not all x86 interrupts can be called in Windows. On the software side of things both Operating Systems are mostly obscured from eachother. This is one of a few things that contributes to the reason why I think its ideal to not mix them up on a wiki-page or whatever. For some programmers focusing on tinytro coding below 1k for DOS specifically dont need all the resources windows tinytro programming need. (There might ofcourse be cases where the machinecode and/or assembly code have a few tricks both platforms can use - but then this has to be specified somewhere and not be related to any OSes on any page) Some whole branches (atleast software-related) are removed in DOS tinytro-coding (specifically for files like COM that are loaded at a pre-set address 0100h). Just running the machinecode and most if not all is programmed in assembly language. No inline-assembly, like phoenix said, compression is something thats just not possible to do in these tiny programs. Atleast not with current compression-technology.

Im sure you allready knew all of this, but a resource site should imho draw a separation between tinytros for DOS and stuff in Windows thats been compressed with Crinkler, or Windows intros in general. They are just too far apart from eachother - atleast in the present moment as I see it.

For me and maybe for others as well coding tinytros for dos is alot like weaving code and data, or more like a puzzle game, because the different sizes of the puzzle pieces does not always fit the required size of the whole image. This might sound a bit strange, but the way to do "compression" is to actually do it manually, that is by finding other means by other opcodes and operands (some people like to call it tricks) to make the code smaller. This is probably a more direct manual way to compress code instead of using a compressor.

I dont want to interfere in any discussion about where to put <1k intro coding material on the web, for me it really does not matter, as long as its separated im fine with it.
And.... its really really late here, so Zzzzz

trixter: i suggest you ensure that loading sizecoding.org behaves the same as loading www.sizecoding.org

I'm hosting multiple virtual domains on a single IP address via CNAME aliases. If you are an apache mod_rewrite guru, I welcome the help.

hmmm...

i would believe the common way to solve it would be to have the dns settings on your provider as:
A @ youripaddress
CNAME www @

and the apache config file with:
<VirtualHost youripaddress:80>
ServerName www.sizecoding.org
DocumentRoot /www/localpathto/sizecoding.org
</VirtualHost>

<VirtualHost youridaddress:80>
ServerName sizecoding.org
Redirect permanent / http://www.sizecoding.org/
</VirtualHost>

don't blame me if everything explodes though :D

i keep telling people i'm not a sysadmin, don't know why people keep asking me to figure these things at work :p

or https://github.com/pouetnet/pouet2.0/blob/master/.htaccess

Neat resource, looked through it a bit, but I doubt I'll ever produce a 256-sized prod. Nice work. :)

@ psenough, ARGH! I really dislike sites these days that redirect to their "www" version, because why? What's the point? "www" is a subdomain made special for historical reasons only. It's far cleaner to omit it unless you need it to identify a URL on physical goods that for brevity you've removed the "http[s]://" from.

(and yes, I know, Pouet does it too... but that doesn't mean I have to like it, or think it's less silly. :P)

Putting "www" at the start makes the url look nice and symmetrical.

well, you can always do it the other way around if you prefer :p
have the main without the www, and the one with www pointing to the bare domain
i just like that both end up on the same place because it's easy to make the mistake of not knowing which one is the main.

@psenough. Why does my iPad need a dress?

:D

Actually, "www" is a hostname, not a subdomain. Entering just a domain and expecting it to go somewhere is considered bad form (despite the fact that many people do it and expect it to work).

I will re-investigate rewrite rules for www.sizecoding.org. In the meantime, y'all should contribute some tips and tricks to it (the ones you don't mind giving up, of course :)

Caused an infinite loop, but I think I've fixed it with a ServerAlias directive. Test and let me know if otherwise.

Works fine, I get a 301 redirect to the www variant.
Not sure why I didn't think about this before, but 301/302 redirects can be done through html meta tags as well... not exactly a robust solution though. :)

Well, if you already set up a subdomain to serve a HTML file with a redirect, then you could just instead make it send a HTTP header too. ;)

yeah, both urls seem to be working :)

Thanks the guys who made this. This is a must have for anybody who want to do some intro democoding.