Forum comments in chronological order
Disclaimer: I am not responsible for what people (other than myself) write in the forums. Please report any abuse, such as insults, slander, spam and illegal material, and I will take appropriate actions. Don't feed the trolls.
Jag tar inget ansvar för det som skrivs i forumet, förutom mina egna inlägg. Vänligen rapportera alla inlägg som bryter mot reglerna, så ska jag se vad jag kan göra. Som regelbrott räknas till exempel förolämpningar, förtal, spam och olagligt material. Mata inte trålarna.
- Jun 2007
- Aug 2007
- Oct 2007
- Nov 2007
- Dec 2007
- Jan 2008
- Feb 2008
- Mar 2008
- Apr 2008
- May 2008
- Jun 2008
- Jul 2008
- Aug 2008
- Sep 2008
- Oct 2008
- Nov 2008
- Dec 2008
- Jan 2009
- Feb 2009
- Mar 2009
- Apr 2009
- May 2009
- Jun 2009
- Jul 2009
- Aug 2009
- Sep 2009
- Oct 2009
- Nov 2009
- Dec 2009
- Jan 2010
- Feb 2010
- Mar 2010
- Apr 2010
- May 2010
- Jun 2010
- Jul 2010
- Aug 2010
- Sep 2010
- Oct 2010
- Nov 2010
- Dec 2010
- Jan 2011
- Feb 2011
- Mar 2011
- Apr 2011
- May 2011
- Jun 2011
- Jul 2011
- Aug 2011
- Sep 2011
- Oct 2011
- Nov 2011
- Dec 2011
- Jan 2012
- Feb 2012
- Mar 2012
- Apr 2012
- May 2012
- Jun 2012
- Jul 2012
- Aug 2012
- Sep 2012
- Oct 2012
- Nov 2012
- Dec 2012
- Jan 2013
- Feb 2013
- Mar 2013
- Apr 2013
- May 2013
- Jun 2013
- Jul 2013
- Aug 2013
- Sep 2013
- Oct 2013
- Nov 2013
- Dec 2013
- Jan 2014
- Feb 2014
- Mar 2014
- Apr 2014
- May 2014
- Jun 2014
- Jul 2014
- Aug 2014
- Sep 2014
- Oct 2014
- Nov 2014
- Dec 2014
- Jan 2015
- Feb 2015
- Mar 2015
- Apr 2015
- May 2015
- Jun 2015
- Jul 2015
- Aug 2015
- Sep 2015
- Oct 2015
- Nov 2015
- Dec 2015
- Jan 2016
- Feb 2016
- Mar 2016
- Apr 2016
- May 2016
- Jun 2016
- Jul 2016
- Aug 2016
- Sep 2016
- Oct 2016
- Nov 2016
- Dec 2016
- Jan 2017
- Feb 2017
- Mar 2017
- Apr 2017
- May 2017
- Jun 2017
- Jul 2017
- Aug 2017
- Sep 2017
- Oct 2017
- Nov 2017
- Dec 2017
- Jan 2018
- Feb 2018
- Mar 2018
- Apr 2018
- May 2018
- Jun 2018
- Jul 2018
- Aug 2018
- Sep 2018
- Oct 2018
- Nov 2018
- Dec 2018
- Jan 2019
- Feb 2019
- Mar 2019
- Apr 2019
- May 2019
- Jun 2019
- Jul 2019
- Aug 2019
- Sep 2019
- Oct 2019
- Nov 2019
- Dec 2019
- Jan 2020
- Feb 2020
- Mar 2020
- Apr 2020
- May 2020
- Jun 2020
- Jul 2020
- Aug 2020
- Sep 2020
- Oct 2020
- Nov 2020
- Dec 2020
- Jan 2021
- Feb 2021
- Mar 2021
- Apr 2021
- May 2021
- Jun 2021
- Jul 2021
- Aug 2021
- Sep 2021
- Oct 2021
- Nov 2021
- Dec 2021
- Jan 2022
- Feb 2022
- Mar 2022
- Apr 2022
- May 2022
- Jun 2022
- Jul 2022
- Aug 2022
- Sep 2022
- Oct 2022
- Nov 2022
- Dec 2022
- Jan 2023
- Feb 2023
- Mar 2023
- Apr 2023
- May 2023
- Jun 2023
- Jul 2023
- Aug 2023
- Sep 2023
- Oct 2023
- Nov 2023
- Dec 2023
- Jan 2024
- Feb 2024
- Mar 2024
- Apr 2024
- May 2024
- Jun 2024
- Jul 2024
- Aug 2024
- Sep 2024
- Oct 2024
- Nov 2024
- Dec 2024
Aug 2009
Anonymous
Mon 3-Aug-2009 06:32
Mon 3-Aug-2009 06:32
You've got a lot of patience to do all of that. I'd say fuck it half through. Keep up the good work though.
A case against syntax highlighting
Anonymous
Fri 7-Aug-2009 22:33
Fri 7-Aug-2009 22:33
Here's something I find handy about syntax highlighting - brackets, in javascript and many other languages its really useful when nesting code.
Anonymous
Mon 10-Aug-2009 07:21
Mon 10-Aug-2009 07:21
Very nice. I'm currently (trying to) write a Unix-clone mostly from scratch, and this is a good resource on how TTYs are supposed to work.
Anonymous
Sun 16-Aug-2009 15:32
Sun 16-Aug-2009 15:32
Hi--how are things in Sweden?
Every once in a while I get up the ambition to complain about the width of text on a web page, and you're the lucky winner today--sorry ;-)
This could be a good article--from the looks of it, it probably is--but why is it (and so many other web pages today) so wide?
Checking one line at random, it is 130 characters wide:
echo "Meanwhile, however, the computers — still quite large and primitive, but able to multitask — were becoming powerful enough to" | wc
1 20 130
Oh, and I'm ignoring the stuff in the left hand panel / column--I simply horizontally scroll so that panel is not visible.
I have three choices if I want to read your article:
* horizontally scroll on each line
* set the type size very small (or zoom out), so an entire line appears on the screen, then use a magnifying glass
* copy and paste the text to a file and read it in an editor--possibly deleting hard line breaks to let the text flow better.
Ideally, and I've seen it done this way, so I believe it can be done:
* the text should be arranged to wrap to the width of the (reader's) window
* if there are long lines of code (pre-formatted text), or wide pictures, or something like that, the other text should still wrap to the width of the reader's window, although he'll have to horizontally scroll to see the full picture or code or whatever. (This is the part I'm specifically referring to as having seen done, but I can't remember any details (like an example, or how to do it--I'll try to pay attention and find some).
Anyway, sorry for the rant--thanks for making the effort to create and disseminate pages with information like this!
Randy Kramer
Every once in a while I get up the ambition to complain about the width of text on a web page, and you're the lucky winner today--sorry ;-)
This could be a good article--from the looks of it, it probably is--but why is it (and so many other web pages today) so wide?
Checking one line at random, it is 130 characters wide:
echo "Meanwhile, however, the computers — still quite large and primitive, but able to multitask — were becoming powerful enough to" | wc
1 20 130
Oh, and I'm ignoring the stuff in the left hand panel / column--I simply horizontally scroll so that panel is not visible.
I have three choices if I want to read your article:
* horizontally scroll on each line
* set the type size very small (or zoom out), so an entire line appears on the screen, then use a magnifying glass
* copy and paste the text to a file and read it in an editor--possibly deleting hard line breaks to let the text flow better.
Ideally, and I've seen it done this way, so I believe it can be done:
* the text should be arranged to wrap to the width of the (reader's) window
* if there are long lines of code (pre-formatted text), or wide pictures, or something like that, the other text should still wrap to the width of the reader's window, although he'll have to horizontally scroll to see the full picture or code or whatever. (This is the part I'm specifically referring to as having seen done, but I can't remember any details (like an example, or how to do it--I'll try to pay attention and find some).
Anyway, sorry for the rant--thanks for making the effort to create and disseminate pages with information like this!
Randy Kramer
Anonymous
Tue 18-Aug-2009 23:13
Tue 18-Aug-2009 23:13
Hello Linus,
Are you planning to release your source code (even without music)?
Are you planning to release your source code (even without music)?
lft
Linus Åkesson
Thu 20-Aug-2009 08:43
Linus Åkesson
Thu 20-Aug-2009 08:43
Hello Linus,
Are you planning to release your source code (even without music)?
Are you planning to release your source code (even without music)?
Hi!
This time I don't have plans to release the source code, because there's nothing particularly new compared to the playroutine in Craft. There's the drum samples, of course, but that's just 1-bit DPCM. Also, getting 44.1 kHz sound from a chip running at 8 MHz was a challenge, but nothing extreme. So the code is a mess, and I feel like I'd have to tidy it up a bit if I were to release it.
A case against syntax highlighting
Anonymous
Sat 29-Aug-2009 23:58
Sat 29-Aug-2009 23:58
/*Second, try this piece of C code:
void main(void)
{
int d, d, ad;
printf("%d%d", dd, ad);
}
void main(void)
{
int d, d, ad;
printf("%d%d", dd, ad);
}
You have another bug, which syntax highlighting is useless for: you double-define 'd', and you use an undefined variable 'dd'. ;)
Anonymous
Sun 30-Aug-2009 00:02
Sun 30-Aug-2009 00:02
I think you have a case for a lot of languages, but one interesting case is that of LateX - without syntax highlighting you really have to stare at the screen to see if you've written \subsection{} which is an operator, or subsection{}, which the typesetter will parse as normal text. By the way, I know that LateX is not a programming language, but I feel it's relevant.
Actually, it is. TeX, the language underneath LaTeX, is fully Turing complete, and a BASIC interpreter for it exists. Google if you don't believe me.
Anonymous
Sun 30-Aug-2009 00:11
Sun 30-Aug-2009 00:11
"Syntax errors will be found by the compiler anyway; the developers shouldn't waste time looking for them." Come on, we all know that syntax highlighting isn't about finding syntax errors. It's about disambiguating between properties and methods, or strings and code blocks. It actually clarifies the semantic content that the syntax might hide.
Properties vs. methods? Syntax. Strings? Syntax. Code blocks? Syntax. Yeah, I'd pretty much have to say that syntax highlighting has *nothing* whatsoever to do with code semantics, and *everything* to do with discovering syntax errors, and quickly.
Syntax highlighting, in all honesty, WAS introduced with the express intent of helping the coder review his code before kicking off a compile. Anyone who has worked in anything beyond a hobby project knows that a compile run can take minutes to complete, even with partial compilation. Who wants to wait that long?
Syntax highlighting is utterly invaluable from a static analysis point of view.
Here's the crux of my counter-argument, and it builds on your notion that semantics is more important than syntax
I only wish that were true. My favorite languages are Forth and Lisp. Yet, nobody codes in these awesome environments. Why? The stack is too hard for people to grok, or, there's too many parentheses.
Let's just all admit it together now: syntax matters, and it matters BIG-TIME.